mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Corey Minyard <minyard@acm.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] MAINTAINERS: exclude char maintainers from things they do not maintain
Date: Wed, 30 Sep 2020 13:02:46 -0700	[thread overview]
Message-ID: <ec0ed7046e170f315a100fbf7c7c2dd9d6f92958.camel@perches.com> (raw)
In-Reply-To: <20200930162828.GA1672130@kroah.com>

On Wed, 2020-09-30 at 18:28 +0200, Greg Kroah-Hartman wrote:
> On Wed, Sep 30, 2020 at 08:36:56AM -0500, Corey Minyard wrote:
> > On Wed, Sep 30, 2020 at 02:10:07PM +0200, Greg Kroah-Hartman wrote:
> > > There are a number of subdirectories and files in drivers/char/ that
> > > have their own maintainers and developers and ways of getting patches to
> > > Linus.  This includes random.c, IPMI, hardware random drivers, TPM
> > > drivers, and agp drivers.  Instead of sending those patches to Arnd and
> > > myself, who can't do anything with them, send them to the proper
> > > developers instead.
> > > 
> > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > Yes, please do.  No reason for you to get all the noise from these.
> > 
> > Acked-by: Corey Minyard <cminyard@mvista.com>
> 
> Thanks!
> 
> greg k-h

Your exclusion list is:

+X:	drivers/char/agp/
+X:	drivers/char/hw_random/
+X:	drivers/char/ipmi/
+X:	drivers/char/random.c
+X:	drivers/char/tpm/

But the current subdirectories of drivers/char are:

drivers/char/agp
drivers/char/hw_random
drivers/char/ipmi
drivers/char/mwave
drivers/char/pcmcia
drivers/char/tpm
drivers/char/tpm/eventlog
drivers/char/tpm/st33zp24
drivers/char/xilinx_hwicap
drivers/char/xillybus

do you want to specifically maintain any of them?

Wouldn't it be easier to add a single subdirectory exclusion
and add specific inclusions for subdirectories you actually
do want to maintain>


X:	drivers/char/*/
F:	drivers/char/<whatever>





  reply	other threads:[~2020-09-30 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 12:10 Greg Kroah-Hartman
2020-09-30 13:19 ` Arnd Bergmann
2020-09-30 16:28   ` Greg Kroah-Hartman
2020-09-30 13:36 ` Corey Minyard
2020-09-30 16:28   ` Greg Kroah-Hartman
2020-09-30 20:02     ` Joe Perches [this message]
2020-10-01  6:29       ` Greg Kroah-Hartman
2020-10-01  6:41         ` Joe Perches
2020-10-01 11:38           ` Greg Kroah-Hartman

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=ec0ed7046e170f315a100fbf7c7c2dd9d6f92958.camel@perches.com \
    --to=joe@perches.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.org \
    /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

all inboxes | Powered by JetHome®