linux-kernel - Re: [PATCH] firmware/google: drop 'select EFI' to avoid recursive dependency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Jan 2014 16:02:07 -0800
From:	Joe Perches <joe@...ches.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	Mike Waychison <mikew@...gle.com>, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware/google: drop 'select EFI' to avoid recursive
 dependency

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@...r.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@...gle.com>
+S:     Supported
+F:     drivers/firmware/google/
+
 GPIO SUBSYSTEM
 M:	Linus Walleij <linus.walleij@...aro.org>
 M:	Alexandre Courbot <gnurou@...il.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/