From: Rami Rosen <ramirose@gmail.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, pablo.de.lara.guarch@intel.com,
akhil.goyal@nxp.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com, Rami Rosen <ramirose@gmail.com>,
stable@dpdk.org
Subject: [dpdk-dev] [PATCH] doc: add guideines for initial PMD submission
Date: Tue, 9 Apr 2019 20:36:35 +0300 [thread overview]
Message-ID: <20190409173635.5127-1-ramirose@gmail.com> (raw)
Message-ID: <20190409173635.SGvgcxt3mtyJo13CzBpwLEaYlQgbYloas6TnIw7c2PI@z> (raw)
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.
+
* New external functions should be added to the local ``version.map`` file.
See the :doc:`Guidelines for ABI policy and versioning </contributing/versioning>`.
New external functions should also be added in alphabetical order.
--
2.19.2
next reply other threads:[~2019-04-09 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 17:36 Rami Rosen [this message]
2019-04-09 17:36 ` Rami Rosen
2019-04-10 10:06 ` Trahe, Fiona
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=20190409173635.5127-1-ramirose@gmail.com \
--to=ramirose@gmail.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=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).