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:	Fri, 24 Jan 2014 02:27:32 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Joe Perches <joe@...ches.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, 23 Jan 2014, Joe Perches wrote:

> > > 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.
> 

I think scripts/get_maintainer.pl is only really useful for emailing 
patches so I think outputting at least somebody to cc on patches would be 
a good idea.  It doesn't necessarily need to be someone who maintains the 
code and pushes it to Linus.

I'm not sure how much runtime is a factor for people of the script, but 
falling back to git-blame behavior to at least get one or two cc's sounds 
appropriate.  If the email address is outdated, owell, we live and learn.

Otherwise it just seems like people would throw patches at a wall and see 
which ones stick.

Now, if Andrew wants an all-encompasing MAINTAINERS entry that really 
lists all the directories he maintains, that would be fine as well just as 
long as we're ok with the size of MAINTAINERS doubling :)
--
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/