If that is the case, then probably a reference to MAINTAINERS should be
mentioned in the documentation
because there are a lot more other stuff(beyond PMDs) in DPDK where people can
contribute and for that people need to
look into MAINTAINERS anyway.
Hi Akhil,
Thanks for your response. It seems
Hi Akhil,
Thanks for your response. It seems to me though that the MAINTAINER file is
not really part of the documentation,
it is more of a reference type of file. Not sure that new DPDK developers
will know to look in it for this type of information.
I will send V2 of the patch and add event and
Hi Fiona,
>[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 "
Thanks for this feedback, I will fix it in V2 of the patch.
Regards,
Rami Rosen
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 men
rko
> ; Rami Rosen ; sta...@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-n
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:
6 matches
Mail list logo