From: Corey Minyard <minyard@acm.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.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 08:36:56 -0500 [thread overview]
Message-ID: <20200930133656.GY3674@minyard.net> (raw)
In-Reply-To: <20200930121007.GA1615300@kroah.com>
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>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d6b9445649e5..a6f0a3ec0047 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4101,6 +4101,11 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> F: drivers/char/
> F: drivers/misc/
> F: include/linux/miscdevice.h
> +X: drivers/char/agp/
> +X: drivers/char/hw_random/
> +X: drivers/char/ipmi/
> +X: drivers/char/random.c
> +X: drivers/char/tpm/
>
> CHECKPATCH
> M: Andy Whitcroft <apw@canonical.com>
next prev parent reply other threads:[~2020-09-30 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 12:10 [PATCH] MAINTAINERS: exclude char maintainers from things they do not maintain 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 [this message]
2020-09-30 16:28 ` Greg Kroah-Hartman
2020-09-30 20:02 ` Joe Perches
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=20200930133656.GY3674@minyard.net \
--to=minyard@acm.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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 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.