From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, ferruh.yigit@amd.com, gakhil@marvell.com,
jerinj@marvell.com, maxime.coquelin@redhat.com
Subject: [PATCH v2] maintainers: assign meson.build for drivers with subtrees
Date: Fri, 1 Sep 2023 14:41:16 +0200 [thread overview]
Message-ID: <20230901124116.711146-1-david.marchand@redhat.com> (raw)
In-Reply-To: <20230901120326.706835-1-david.marchand@redhat.com>
When a new (for example, net) driver gets submitted, the CI scripts
can't determine which subtree (here, dpdk-next-net) this series is
associated to because the MAINTAINERS update for the new driver is
part of the series.
Put meson.build of the drivers classes under the responsibility of
subtree maintainers.
While at it, cleanup redundant statements:
- Ferruh or Jerin are maintainers of next-net / next-event but this
information is already present at the top of the MAINTAINERS file,
- the subtree for baseband drivers can be put at the start of the
baseband section,
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
Changes since v1:
- added some minor cleanup,
---
MAINTAINERS | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a926155f26..f3e3dda872 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -609,8 +609,8 @@ F: drivers/bus/vmbus/
Networking Drivers
------------------
-M: Ferruh Yigit <ferruh.yigit@amd.com>
T: git://dpdk.org/next/dpdk-next-net
+F: drivers/net/meson.build
F: doc/guides/nics/features/default.ini
Link bonding
@@ -1057,6 +1057,7 @@ F: doc/guides/nics/features/memif.ini
Crypto Drivers
--------------
T: git://dpdk.org/next/dpdk-next-crypto
+F: drivers/crypto/meson.build
F: doc/guides/cryptodevs/features/default.ini
AMD CCP Crypto
@@ -1193,6 +1194,7 @@ F: doc/guides/cryptodevs/features/virtio.ini
Compression Drivers
-------------------
T: git://dpdk.org/next/dpdk-next-crypto
+F: drivers/compress/meson.build
Cavium OCTEON TX zipvf
M: Ashish Gupta <ashish.gupta@marvell.com>
@@ -1290,6 +1292,7 @@ F: doc/guides/mldevs/cnxk.rst
vDPA Drivers
------------
T: git://dpdk.org/next/dpdk-next-virtio
+F: drivers/vdpa/meson.build
Intel ifc
M: Xiao Wang <xiao.w.wang@intel.com>
@@ -1313,8 +1316,8 @@ F: doc/guides/vdpadevs/features/sfc.ini
Eventdev Drivers
----------------
-M: Jerin Jacob <jerinj@marvell.com>
T: git://dpdk.org/next/dpdk-next-eventdev
+F: drivers/event/meson.build
Cavium OCTEON TX ssovf
M: Jerin Jacob <jerinj@marvell.com>
@@ -1369,10 +1372,11 @@ F: doc/guides/eventdevs/opdl.rst
Baseband Drivers
----------------
+T: git://dpdk.org/next/dpdk-next-baseband
+F: drivers/baseband/meson.build
Intel baseband
M: Nicolas Chautru <nicolas.chautru@intel.com>
-T: git://dpdk.org/next/dpdk-next-baseband
F: drivers/baseband/turbo_sw/
F: doc/guides/bbdevs/turbo_sw.rst
F: doc/guides/bbdevs/features/turbo_sw.ini
@@ -1391,7 +1395,6 @@ F: doc/guides/bbdevs/features/vrb1.ini
Null baseband
M: Nicolas Chautru <nicolas.chautru@intel.com>
-T: git://dpdk.org/next/dpdk-next-baseband
F: drivers/baseband/null/
F: doc/guides/bbdevs/null.rst
F: doc/guides/bbdevs/features/null.ini
@@ -1399,7 +1402,6 @@ F: doc/guides/bbdevs/features/null.ini
NXP LA12xx
M: Gagandeep Singh <g.singh@nxp.com>
M: Hemant Agrawal <hemant.agrawal@nxp.com>
-T: git://dpdk.org/next/dpdk-next-baseband
F: drivers/baseband/la12xx/
F: doc/guides/bbdevs/la12xx.rst
F: doc/guides/bbdevs/features/la12xx.ini
--
2.41.0
next prev parent reply other threads:[~2023-09-01 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 12:03 [PATCH] " David Marchand
2023-09-01 12:28 ` Thomas Monjalon
2023-09-01 12:33 ` David Marchand
2023-09-01 12:41 ` David Marchand [this message]
2023-09-01 12:57 ` [PATCH v2] " Thomas Monjalon
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=20230901124116.711146-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
/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).