From: Akhil Goyal <akhil.goyal@nxp.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: add guideines for initial PMD submission
Date: Wed, 10 Apr 2019 14:49:52 +0000 [thread overview]
Message-ID: <VI1PR04MB4893AAEE81664AF295D3F9A2E62E0@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190410144952.KtWbJuJ3fqA_LCFFFu5b9AijhoCEbybrA7nisXzhqjU@z> (raw)
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 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 bbdev.
Regards,
Rami Rosen
next reply other threads:[~2019-04-10 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 14:49 Akhil Goyal [this message]
2019-04-10 14:49 ` Akhil Goyal
-- strict thread matches above, loose matches on Subject: below --
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-09 17:36 Rami Rosen
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
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=VI1PR04MB4893AAEE81664AF295D3F9A2E62E0@VI1PR04MB4893.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@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).