From: Lee Jones <lee.jones@linaro.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: joe@perches.com, "Theodore Ts'o" <tytso@mit.edu>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Laura Abbott <labbott@redhat.com>,
linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org
Subject: Re: [PATCH] get_maintainer: Don't fallback to git by default
Date: Tue, 27 Oct 2015 10:10:22 +0000 [thread overview]
Message-ID: <20151027101022.GA5828@x1> (raw)
In-Reply-To: <20151027092411.GA3405@katana>
On Tue, 27 Oct 2015, Wolfram Sang wrote:
> > Anyone south of Wolfram and north of the I2C ML is unlikely to care.
>
> Actually, driver maintainers should care about their portion of it.
> Which leads me to the conclusion that driver maintainer entries in
> MAINTAINERS should have the relevant Kconfig symbol as a keyword match,
> probably.
Good point, well put. Although this situation is fairly unique to
Kconfig changes. In general I know I don't want to be spammed with
changes to all the files I've ever adapted though. If people wish to
act as reviewers, they should have a mention in MAINTAINERS for
get_maintiner.pl to pull information from:
R: Designated reviewer: FullName <address@domain>
These reviewers should be CCed on patches.
Or a new marker, I: Interested parties.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-10-27 10:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 22:11 [PATCH] get_maintainer: Don't fallback to git by default Javier Martinez Canillas
2015-10-26 23:00 ` Laura Abbott
2015-10-27 0:08 ` Javier Martinez Canillas
2015-10-27 2:47 ` Theodore Ts'o
2015-10-27 4:57 ` joe
2015-10-27 5:03 ` Laura Abbott
2015-10-27 8:21 ` Lee Jones
2015-10-27 9:24 ` Wolfram Sang
2015-10-27 10:10 ` Lee Jones [this message]
2015-10-27 10:29 ` Wolfram Sang
2015-10-27 17:49 ` Joe Perches
2015-10-27 18:21 ` Joe Perches
2015-10-27 23:25 ` Wolfram Sang
2015-10-27 23:37 ` Joe Perches
2015-10-28 0:05 ` Wolfram Sang
2015-10-28 0:14 ` Joe Perches
2015-10-28 8:50 ` Lee Jones
2015-10-27 17:53 ` Joe Perches
2015-10-27 18:09 ` Lee Jones
2015-10-27 19:24 ` Javier Martinez Canillas
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=20151027101022.GA5828@x1 \
--to=lee.jones@linaro.org \
--cc=javier@osg.samsung.com \
--cc=joe@perches.com \
--cc=labbott@redhat.com \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wsa@the-dreams.de \
/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.