linux-kernel - Re: [patch] MAINTAINERS: trim the file triggers for ABI/API

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] [day] [month] [year] [list]

Date:	Thu, 04 Feb 2016 12:55:28 -0800
From:	Joe Perches <joe@...ches.com>
To:	Josh Triplett <josh@...htriplett.org>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Linux API <linux-api@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>,
	Steven Rostedt <rostedt@...dmis.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Shuah Khan <shuahkh@....samsung.com>,
	Mauro Carvalho Chehab <mchehab@....samsung.com>
Subject: Re: [patch] MAINTAINERS: trim the file triggers for ABI/API

On Thu, 2016-02-04 at 07:34 -0800, Josh Triplett wrote:
> On Thu, Feb 04, 2016 at 03:05:19PM +0100, Michael Kerrisk (man-pages) wrote:

> Might I suggest an alternate commit message?
> 
> """
> Commit ea8f8fc8631 ("MAINTAINERS: add linux-api for review of API/ABI
> changes") added file triggers for various paths that likely indicated
> API/ABI changes.  However, catching all changes in Documentation/ABI/
> and include/uapi/ produces a large volume of mail to linux-api, rather
> than only API/ABI changes.  Drop those two entries, but leave
> include/linux/syscalls.h and kernel/sys_ni.c to catch syscall-related
> changes.
> """
[]
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@ -223,9 +223,7 @@ F:  drivers/scsi/aacraid/
> > 
> >  ABI/API
> >  L:     linux-api@...r.kernel.org
> > -F:     Documentation/ABI/
> >  F:     include/linux/syscalls.h
> > -F:     include/uapi/
> >  F:     kernel/sys_ni.c

Maybe add a keyword entry like:

K:	(?i)syscall

to see all actual changes of syscalls too?