DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add guideines for initial PMD submission
Date: Wed, 10 Apr 2019 10:06:12 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B4358973D6A7@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20190409173635.5127-1-ramirose@gmail.com>

Hi Rami,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Tuesday, April 9, 2019 6:37 PM
> To: dev@dpdk.org
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> akhil.goyal@nxp.com; Mcnamara, John <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>; Rami Rosen <ramirose@gmail.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: add guideines for initial PMD submission
> 
> This patch for DPDK Contributor's Guidelines indicates the repos
> against which a new PMD should be prepared; for new network ethernet
> PMDs it should be dpdk-next-net, and for new crypto PMDs
> it should be dpdk-next-crypto. Though this may seem obvious, it
> is not mentioned in DPDK documentation.
> 
> Cc: stable@dpdk.org
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
>  doc/guides/contributing/patches.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
> index d8404e623..4dde8e724 100644
> --- a/doc/guides/contributing/patches.rst
> +++ b/doc/guides/contributing/patches.rst
> @@ -148,6 +148,10 @@ Make your planned changes in the cloned ``dpdk`` repo. Here are some
> guidelines
> 
>  * If you add new files or directories you should add your name to the ``MAINTAINERS`` file.
> 
> +* If you add a new network PMD you should prepare the initial submission against dpdk-next-net repo.
> +
> +* If you add a new crypto PMD you should prepare the initial submission against dpdk-next-crypto repo.
[Fiona] Good idea to add this patch. However despite the name crypto is actual broader.... so maybe
"If you add a new crypto or compression PMD.... "

  parent reply	other threads:[~2019-04-10 10:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 17:36 Rami Rosen
2019-04-09 17:36 ` Rami Rosen
2019-04-10 10:06 ` Trahe, Fiona [this message]
2019-04-10 10:06   ` Trahe, Fiona
2019-04-10 14:36   ` Rami Rosen
2019-04-10 14:36     ` Rami Rosen
2019-04-10 10:28 Akhil Goyal
2019-04-10 10:28 ` Akhil Goyal
2019-04-10 14:40 ` Rami Rosen
2019-04-10 14:40   ` Rami Rosen
2019-04-10 14:49 Akhil Goyal
2019-04-10 14:49 ` Akhil Goyal

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=348A99DA5F5B7549AA880327E580B4358973D6A7@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=ramirose@gmail.com \
    --cc=stable@dpdk.org \
    /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).