linux-kernel - Re: [PATCH 2/2] MAINTAINERS: ARM Versatile Express platform

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:	Wed, 26 Nov 2014 07:40:21 -0800
From:	Joe Perches <joe@...ches.com>
To:	Pawel Moll <pawel.moll@....com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Mike Turquette <mturquette@...aro.org>,
	"arm@...nel.org" <arm@...nel.org>,
	Russell King <linux@....linux.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Liviu Dudau <Liviu.Dudau@....com>,
	Sudeep Holla <Sudeep.Holla@....com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: ARM Versatile Express platform

On Wed, 2014-11-26 at 14:40 +0000, Pawel Moll wrote:
> On Wed, 2014-11-26 at 12:17 +0000, Arnd Bergmann wrote:
> > On Wednesday 26 November 2014 12:04:09 Pawel Moll wrote:
> > > 
> > > Right, of course. Whole directory.
> > > 
> > > > F:    */*/vexpress*
> > > 
> > > Cool, didn't think about multiple wildcards. 
> > 
> > Actually, I think you could even do this as
> > 
> > N:	vexpress
> > 
> > which would be even shorter and match most of the other entries too.
> 
> If you think it's safe, fine with me. It would reduce this section to:
> 
> N:	vexpress
> F:	drivers/clocksource/versatile.c

Yes, that's possible too, but:

from MAINTAINERS:

	   scripts/get_maintainer.pl has different behavior for files that
	   match F: pattern and matches of N: patterns.  By default,
	   get_maintainer will not look at git log history when an F: pattern
	   match occurs.  When an N: match occurs, git log history is used
	   to also notify the people that have git commit signatures.

I think it's better to use F: entries because
there is a get_maintainer difference in behavior
between N: and F: entries.

An N: entry means get_maintainer will also cc
patch submitters for these files.

An F: entry will not.


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