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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 27 Oct 2015 10:10:22 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Wolfram Sang <wsa@...-dreams.de>
Cc:	joe@...ches.com, Theodore Ts'o <tytso@....edu>,
	Javier Martinez Canillas <javier@....samsung.com>,
	Laura Abbott <labbott@...hat.com>,
	linux-kernel@...r.kernel.org, linux-kernel-owner@...r.kernel.org
Subject: Re: [PATCH] get_maintainer: Don't fallback to git by default

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@...ain>
   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
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ