All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com, gakhil@marvell.com,
	jerinj@marvell.com, maxime.coquelin@redhat.com
Subject: Re: [PATCH v2] maintainers: assign meson.build for drivers with subtrees
Date: Fri, 01 Sep 2023 14:57:12 +0200	[thread overview]
Message-ID: <18212191.sWSEgdgrri@thomas> (raw)
In-Reply-To: <20230901124116.711146-1-david.marchand@redhat.com>

01/09/2023 14:41, 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.
> 
> 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>

Applied, thanks.




      reply	other threads:[~2023-09-01 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 12:03 [PATCH] maintainers: assign meson.build for drivers with subtrees David Marchand
2023-09-01 12:28 ` Thomas Monjalon
2023-09-01 12:33   ` David Marchand
2023-09-01 12:41 ` [PATCH v2] " David Marchand
2023-09-01 12:57   ` Thomas Monjalon [this message]

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=18212191.sWSEgdgrri@thomas \
    --to=thomas@monjalon.net \
    --cc=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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.