From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: dev@dpdk.org, "Richardson, Bruce" <bruce.richardson@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>, dpdk-dev <dev@dpdk.org>,
Xiaoyun Li <xiaoyun.li@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] examples: move vendor specific apps to drivers sub directory
Date: Wed, 17 Nov 2021 12:02:54 +0100 [thread overview]
Message-ID: <2681457.muES2lAPIp@thomas> (raw)
In-Reply-To: <CALBAE1MWJdV4wXGT4yHyegXysjBKQSJUuxN=S7HwEZfQiOao+A@mail.gmail.com>
05/07/2021 10:53, Jerin Jacob:
> On Thu, Jun 17, 2021 at 12:47 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 26/05/2021 09:47, Hemant Agrawal:
> > > As approved by DPDK technical board on 2021-03-24 NTB and IOAT
> > > raw driver's example application will be moved to
> > > example/drivers/raw/ to avoid PMD specific example application
> >
> > examples with a s :)
> >
> > > to show up in examples directory.
> > >
> > > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > > ---
> > > examples/{ => drivers/raw}/ioat/Makefile | 0
> > > examples/{ => drivers/raw}/ioat/ioatfwd.c | 0
> > > examples/{ => drivers/raw}/ioat/meson.build | 0
> > > examples/{ => drivers/raw}/ntb/Makefile | 0
> > > examples/{ => drivers/raw}/ntb/meson.build | 0
> > > examples/{ => drivers/raw}/ntb/ntb_fwd.c | 0
> >
> > I'm afraid the name is confusing.
> > We could expect some driver example in such a path,
> > but it is just an use of the driver.
> >
> > Any other idea of naming?
>
> Like Linux kernel, Skelton drivers can be added in drivers/ itself, like
> the one existing (drivers/event/skeleton/).
>
> If there are no better suggestions, examples/drivers/raw/.. looks good to me.
It could have been examples/rawdev/ntb/
next prev parent reply other threads:[~2021-11-17 11:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 7:47 [dpdk-dev] [PATCH 1/2] doc: add policy for adding vendor PMD specific examples Hemant Agrawal
2021-05-26 7:47 ` [dpdk-dev] [PATCH 2/2] examples: move vendor specific apps to drivers sub directory Hemant Agrawal
2021-06-17 7:17 ` Thomas Monjalon
2021-07-05 8:53 ` Jerin Jacob
2021-11-17 11:02 ` Thomas Monjalon [this message]
2021-07-05 8:49 ` Jerin Jacob
2021-11-17 11:01 ` Thomas Monjalon
2021-07-05 8:47 ` [dpdk-dev] [PATCH 1/2] doc: add policy for adding vendor PMD specific examples Jerin Jacob
2021-11-17 10:57 ` Thomas Monjalon
2023-07-03 23:30 ` Stephen Hemminger
2023-07-05 9:56 ` [v2 " Hemant Agrawal
2023-07-05 9:56 ` [v2 2/2] examples: move vendor specific apps to drivers sub directory Hemant Agrawal
2024-10-04 2:59 ` Stephen Hemminger
2023-07-06 5:00 ` [v2 1/2] doc: add policy for adding vendor PMD specific examples Jerin Jacob
2023-10-31 20:02 ` Stephen Hemminger
2024-10-04 2:59 ` Stephen Hemminger
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=2681457.muES2lAPIp@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinjacobk@gmail.com \
--cc=jingjing.wu@intel.com \
--cc=xiaoyun.li@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).