From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: n-reply-to=1647557234-37592-1-git-send-email-nicolas.chautru@intel.com,
--cc@dpdk.org, trix@redhat.com, --to@dpdk.org,
thomas@monjalon.net, -cc@dpdk.org, ray.kinsella@intel.com,
-cc@dpdk.org, bruce.richardson@intel.com, --cc@dpdk.org,
hemant.agrawal@nxp.com, --cc@dpdk.org, mingshan.zhang@intel.com,
--cc@dpdk.org, david.marchand@redhat.com,
--ccstephen@networkplumber.orgFrom,
6438b82cf39bb76f1d9e91be0b846e8bd8bbd4c6@dpdk.org, Mon@dpdk.org,
Sep@dpdk.org, 17@dpdk.org, "00:00:00"@dpdk.org, 2001@dpdk.org
Subject: From: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Mon, 21 Mar 2022 11:19:49 -0700 [thread overview]
Message-ID: <1647886790-135829-1-git-send-email-nicolas.chautru@intel.com> (raw)
v4: edits suggested by Thomas
v3: squash issue in v2
v2: adding suggested updates from Thomas and David to split and fix maintainers list, let me know.
--
Suggested by Bruce to add explicit maintainer for some of the existing bbdev PMDs even it is already implicit currently.
Intent is to be easier for user to get a hit when looking for a specific PMD.
Nicolas Chautru (1):
maintainers: add explicit maintainer for some bbdev PMDs
MAINTAINERS | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-03-21 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:19 Nicolas Chautru [this message]
2022-03-21 18:19 ` [PATCH v4] maintainers: add explicit maintainer for some bbdev PMDs Nicolas Chautru
2022-03-29 9:58 ` Thomas Monjalon
2022-09-24 0:50 From: Nicolas Chautru <nicolas.chautru@intel.com> Nicolas Chautru
2022-09-29 21:11 Nicolas Chautru
2022-10-07 19:03 Nicolas Chautru
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=1647886790-135829-1-git-send-email-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc="00:00:00"@dpdk.org \
--cc=--cc@dpdk.org \
--cc=--ccstephen@networkplumber.orgFrom \
--cc=--to@dpdk.org \
--cc=-cc@dpdk.org \
--cc=17@dpdk.org \
--cc=2001@dpdk.org \
--cc=6438b82cf39bb76f1d9e91be0b846e8bd8bbd4c6@dpdk.org \
--cc=Mon@dpdk.org \
--cc=Sep@dpdk.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@intel.com \
--cc=n-reply-to=1647557234-37592-1-git-send-email-nicolas.chautru@intel.com \
--cc=ray.kinsella@intel.com \
--cc=thomas@monjalon.net \
--cc=trix@redhat.com \
/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).