d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: add guidelines for initial PMD submission

Browse Source 
This patch for DPDK Contributor's Guidelines indicates the repos
against which a new PMD should be prepared; for example, for new
network ethernet PMDs it should be dpdk-next-net, and for new crypto
PMDs it should be dpdk-next-crypto. For other new PMDs, the
contributor should refer to the MAINTAINERS file. Though this may seem
obvious, it is not mentioned in DPDK documentation.

Signed-off-by: Rami Rosen <ramirose@gmail.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>

Last contribution, last commit closing the release.
Thank you Rami, you will be missed.
This commit is contained in:
Rami Rosen 2019-04-12 13:26:51 +03:00 committed by Thomas Monjalon
parent f6feb39c20
commit 78b04aaf77
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/guides/contributing/patches.rst
View File

@ -146,6 +146,16 @@ 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.
* Initial submission of new PMDs should be prepared against a corresponding repo.
* Thus, for example, initial submission of a new network PMD should be
prepared against dpdk-next-net repo.
* Likewise, initial submission of a new crypto or compression PMD should be
prepared against dpdk-next-crypto repo.
* For other PMDs and more info, refer to the ``MAINTAINERS`` file.
* 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.