From: Joe Perches <joe@perches.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] MAINTAINERS: Add linux-api for review of API/ABI changes
Date: Wed, 07 May 2014 11:00:43 -0700 [thread overview]
Message-ID: <1399485643.2911.12.camel@joe-AO725> (raw)
In-Reply-To: <5369C37A.1000001@gmail.com>
On Wed, 2014-05-07 at 07:24 +0200, Michael Kerrisk (man-pages) wrote:
> On 05/06/2014 10:59 PM, Josh Triplett wrote:
> > This makes it more likely that patch submitters will CC API/ABI changes
> > to the linux-api list, and tools like get_maintainer.pl will do so
> > automatically.
> >
> > Signed-off-by: Josh Triplett <josh@joshtriplett.org>
> > Acked-by: Steven Rostedt <rostedt@goodmis.org>
>
> Every little bit helps, I guess. However, what I think would make a difference
> is if if people constantly posted reminders to CC linux-api when they see API/API
> changes on the lists. (And the reminders should of course CC linux-api).
[]
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > +ABI/API
> > +L: linux-api@vger.kernel.org
> > +F: Documentation/ABI/
> > +F: include/linux/syscalls.h
> > +F: include/uapi/
> > +F: kernel/sys_ni.c
Perhaps this should have a
"S: Odd Fixes"
line too.
prev parent reply other threads:[~2014-05-07 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 20:59 [PATCH] MAINTAINERS: Add linux-api for review of API/ABI changes Josh Triplett
2014-05-07 5:24 ` Michael Kerrisk (man-pages)
2014-05-07 18:00 ` Joe Perches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1399485643.2911.12.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).