Hi Rami, > > > > 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: [email protected] > > Signed-off-by: Rami Rosen <[email protected]> > > --- > > 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.... "
I believe this information is already captured in the MAINTAINERS file about which PMD goes to which tree. If we need to document it in the documentation as well, then probably all other stuff should also be captured (like event and bbdev) -Akhil
