All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "Tu, Lijuan" <lijuan.tu@intel.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	Aaron Conole <aconole@redhat.com>,
	"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
	Owen Hilyard <ohilyard@iol.unh.edu>,
	"dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>
Cc: nd <nd@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] DTS Workgroup: MoM 06/09/2021
Date: Wed, 16 Jun 2021 06:57:03 +0000	[thread overview]
Message-ID: <2da7b651177549bdb0dcb9d8531b0b8e@pantheon.tech> (raw)
In-Reply-To: <a484a95a07da47bf8c26b18b86c030c2@intel.com>

Hi Lijuan,

I've given you the permissions, can you try now?

Juraj

> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Tu, Lijuan
> Sent: Wednesday, June 16, 2021 7:37 AM
> To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Aaron Conole
> <aconole@redhat.com>; Lincoln Lavoie <lylavoie@iol.unh.edu>; Owen Hilyard
> <ohilyard@iol.unh.edu>; dev@dpdk.org; dts@dpdk.org
> Cc: nd <nd@arm.com>; nd <nd@arm.com>
> Subject: Re: [dts] DTS Workgroup: MoM 06/09/2021
> 
> Hi Honnappa,
> 
> I can't edit the file "DTS DPDK modifications", could you give me access?
> 
> > -----Original Message-----
> > From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> > Sent: 2021年6月16日 13:30
> > To: Aaron Conole <aconole@redhat.com>; Tu, Lijuan
> > <lijuan.tu@intel.com>; Lincoln Lavoie <lylavoie@iol.unh.edu>; Owen
> > Hilyard <ohilyard@iol.unh.edu>; dev@dpdk.org; dts@dpdk.org
> > Cc: nd <nd@arm.com>; Honnappa Nagarahalli
> > <Honnappa.Nagarahalli@arm.com>; nd <nd@arm.com>
> > Subject: DTS Workgroup: MoM 06/09/2021
> >
> > Attendees:
> > Aaron Conole
> > Honnappa Nagarahalli
> > Lijuan Tu
> > Lincoln Lavoie
> > Owen Hilyard
> >
> > The meeting announcements are sent to dev@dpdk.org.
> >
> > Minutes:
> > 1) The work item related discussions are captured in [1]
> >
> > Action Items:
> > 1) Review [2] and understand how the code changes can be removed.
> > Categorize the code changes into
> > 	a) We could create a bug report against DPDK if it makes sense to
> > change DPDK (for ex: enhance testpmd to provide additional info)
> > 	b) The test case might be testing something for which an API might
> > not exist. Decide if a new API is required in DPDK.
> > 	c) If the test case is not valid, decide to remove the test case -
> > Lijuan Tu
> >
> > [1] https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-
> > qNvUb-fBdjA6DGusy4yM/edit?usp=sharing
> > [2]
> > https://docs.google.com/spreadsheets/d/1i7x4ecPiRXNKOrOy0the5WyGSWb
> > dMxPLK7aWbuWI4ew/edit#gid=880561943


      reply	other threads:[~2021-06-16  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  5:30 [dpdk-dev] DTS Workgroup: MoM 06/09/2021 Honnappa Nagarahalli
2021-06-16  5:36 ` Tu, Lijuan
2021-06-16  6:57   ` Juraj Linkeš [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2da7b651177549bdb0dcb9d8531b0b8e@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.