DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: thomas@monjalon.net, hemant.agrawal@nxp.com,
	mingshan.zhang@intel.com, david.marchand@redhat.com,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v2] maintainers: add explicit maintainer for some bbdev PMDs
Date: Thu, 17 Mar 2022 14:45:53 -0700	[thread overview]
Message-ID: <1647553553-36995-2-git-send-email-nicolas.chautru@intel.com> (raw)
In-Reply-To: <1647553553-36995-1-git-send-email-nicolas.chautru@intel.com>

These were implicit from DPDK script but adding
separate reference to make it explicit.
Separate sections for API and PMDs

Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
---
 MAINTAINERS | 32 ++++++++++++++++++++++++++------
 1 file changed, 26 insertions(+), 6 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index a3b4f5a..45b30e5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -421,12 +421,7 @@ M: Nicolas Chautru <nicolas.chautru@intel.com>
 T: git://dpdk.org/next/dpdk-next-crypto
 F: lib/bbdev/
 F: doc/guides/prog_guide/bbdev.rst
-F: drivers/baseband/
-F: drivers/baseband/turbo_sw/
-F: drivers/baseband/fpga_lte_fec/
-F: drivers/baseband/fpga_5gnr_fec/
-F: drivers/baseband/acc100/
-F: doc/guides/bbdevs/
+F: doc/guides/bbdevs/features/default.ini
 F: app/test-bbdev/
 F: doc/guides/tools/testbbdev.rst
 F: examples/bbdev_app/
@@ -1303,11 +1298,36 @@ F: doc/guides/eventdevs/opdl.rst
 Baseband Drivers
 ----------------
 
+Intel PMDs
+M: Nicolas Chautru <nicolas.chautru@intel.com>
+T: git://dpdk.org/next/dpdk-next-crypto
+F: drivers/baseband/turbo_sw/
+F: drivers/baseband/fpga_lte_fec/
+F: drivers/baseband/fpga_5gnr_fec/
+F: drivers/baseband/acc100/
+F: doc/guides/bbdevs/turbo_sw.rst
+F: doc/guides/bbdevs/fpga_lte_fec.rst
+F: doc/guides/bbdevs/fpga_5gnr_fec.rst
+F: doc/guides/bbdevs/acc100.rst
+F: doc/guides/bbdevs/features/turbo_sw.ini
+F: doc/guides/bbdevs/features/fpga_lte_fec.ini
+F: doc/guides/bbdevs/features/fpga_5gnr_fec.ini
+F: doc/guides/bbdevs/features/acc100.ini
+
+Null bbdev PMD
+M: Nicolas Chautru <nicolas.chautru@intel.com>
+T: git://dpdk.org/next/dpdk-next-crypto
+F: drivers/baseband/null/
+F: doc/guides/bbdevs/null.rst
+F: doc/guides/bbdevs/features/null.ini
+
 NXP LA12xx
 M: Nipun Gupta <nipun.gupta@nxp.com>
 M: Hemant Agrawal <hemant.agrawal@nxp.com>
+T: git://dpdk.org/next/dpdk-next-crypto
 F: drivers/baseband/la12xx/
 F: doc/guides/bbdevs/la12xx.rst
+F: doc/guides/bbdevs/features/la12xx.ini
 
 
 GPU Drivers
-- 
1.8.3.1


  reply	other threads:[~2022-03-17 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 21:45 Nicolas Chautru
2022-03-17 21:45 ` Nicolas Chautru [this message]
2022-03-18 20:29   ` Thomas Monjalon
2022-03-17 22:47 Nicolas Chautru
2022-03-17 22:47 ` 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=1647553553-36995-2-git-send-email-nicolas.chautru@intel.com \
    --to=nicolas.chautru@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=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).