From: Joe Perches <joe@perches.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mike Waychison <mikew@google.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware/google: drop 'select EFI' to avoid recursive dependency
Date: Thu, 23 Jan 2014 16:02:07 -0800 [thread overview]
Message-ID: <1390521727.32356.16.camel@joe-AO722> (raw)
In-Reply-To: <alpine.DEB.2.02.1401231444510.26509@chino.kir.corp.google.com>
On Thu, 2014-01-23 at 14:45 -0800, David Rientjes wrote:
> On Thu, 23 Jan 2014, Andrew Morton wrote:
>
> > > $ ./scripts/get_maintainer.pl -f drivers/firmware/google/Kconfig
> > > linux-kernel@vger.kernel.org (open list)
> > >
> > > I wonder why he's not listed as a recipient for patches from
> > > get_maintainer.pl since it's clearly obvious he wrote the entire file.
> >
> > I do wish get_maintainer was better about this. You can apparently
> > make it dtrt with funky arguments, but --git-since and --git aren't
> > working for me.
Or use --interactive to figure out what's what when it
doesn't give you an answer you like.
> >
> > get_maintainer's default output should answer the question "who do I
> > email about this file", and that ain't working :(
Complaints cheerfully ignored.
Suggestions gratefully accepted.
Files that haven't had changes in a long time
generally aren't maintained.
Old addresses frequently become stale and bounce.
It'd be better if there was a MAINTAINERS entry
for drivers/firmware/google.
Far be it for me to volunteer someone to be a
maintainer though.
Something like:
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5c5d554..f4271d5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3802,6 +3802,11 @@ F: Documentation/isdn/README.gigaset
F: drivers/isdn/gigaset/
F: include/uapi/linux/gigaset_dev.h
+GOOGLE MEMORY CONSOLE
+M: Mike Waychison <mikew@google.com>
+S: Supported
+F: drivers/firmware/google/
+
GPIO SUBSYSTEM
M: Linus Walleij <linus.walleij@linaro.org>
M: Alexandre Courbot <gnurou@gmail.com>
> >
>
> I also think it would be great if get_maintainer's output was friendlier
> so that I can just copy a comma-separated line of "name <email>, name2
> <email2>" into my email client.
That's what it was, then people complained about not knowing
what the people did to the particular files being modified
and the default became --rolestats.
You can get that comma separated list by adding
--norolestats --nomultiline
next prev parent reply other threads:[~2014-01-24 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 10:39 Ard Biesheuvel
2014-01-23 21:36 ` David Rientjes
2014-01-23 21:40 ` Mike Waychison
2014-01-23 21:48 ` Ard Biesheuvel
2014-01-23 21:49 ` Andrew Morton
2014-01-23 22:45 ` David Rientjes
2014-01-24 0:02 ` Joe Perches [this message]
2014-01-24 10:27 ` David Rientjes
2014-01-24 22:56 ` Joe Perches
2014-01-24 23:17 ` David Rientjes
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=1390521727.32356.16.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=rientjes@google.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 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®