diff mbox series

maintainers: assign meson.build for drivers with subtrees

Message ID 20230901120326.706835-1-david.marchand@redhat.com (mailing list archive)
State Superseded, archived
Delegated to: Thomas Monjalon
Headers
Series maintainers: assign meson.build for drivers with subtrees |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/loongarch-compilation success Compilation OK
ci/loongarch-unit-testing success Unit Testing PASS
ci/Intel-compilation success Compilation OK
ci/intel-Testing success Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-compile-amd64-testing success Testing PASS
ci/iol-unit-amd64-testing fail Testing issues
ci/iol-unit-arm64-testing success Testing PASS
ci/iol-sample-apps-testing success Testing PASS
ci/intel-Functional success Functional PASS
ci/iol-intel-Performance success Performance Testing PASS
ci/iol-compile-arm64-testing success Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-broadcom-Functional success Functional Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS

Commit Message

David Marchand Sept. 1, 2023, 12:03 p.m. UTC 
  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.

Signed-off-by: David Marchand <david.marchand@redhat.com>
---
 MAINTAINERS | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

Comments

Thomas Monjalon Sept. 1, 2023, 12:28 p.m. UTC | #1 
01/09/2023 14:03, David Marchand:
> 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.
[...]
> @@ -1315,6 +1319,7 @@ Eventdev Drivers
>  ----------------
>  M: Jerin Jacob <jerinj@marvell.com>
>  T: git://dpdk.org/next/dpdk-next-eventdev
> +F: drivers/event/meson.build

While at it, can we remove Jerin's name here?
He's already referenced for the whole git tree at the beginning of the file.
Other device classes don't add a name for drivers, it is redundant.
David Marchand Sept. 1, 2023, 12:33 p.m. UTC | #2 
On Fri, Sep 1, 2023 at 2:28 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 01/09/2023 14:03, David Marchand:
> > 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.
> [...]
> > @@ -1315,6 +1319,7 @@ Eventdev Drivers
> >  ----------------
> >  M: Jerin Jacob <jerinj@marvell.com>
> >  T: git://dpdk.org/next/dpdk-next-eventdev
> > +F: drivers/event/meson.build
>
> While at it, can we remove Jerin's name here?
> He's already referenced for the whole git tree at the beginning of the file.
> Other device classes don't add a name for drivers, it is redundant.

The same is true for Ferruh too.
v2 on the way.
diff mbox series

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index a926155f26..598edadc42 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -611,6 +611,7 @@  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 +1058,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 +1195,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 +1293,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>
@@ -1315,6 +1319,7 @@  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 +1374,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 +1397,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 +1404,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