ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizefan@huawei.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Reviewing new API/ABI
Date: Thu, 8 May 2014 14:35:25 +0800	[thread overview]
Message-ID: <536B25AD.8040502@huawei.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1405071343390.3969@pobox.suse.cz>

On 2014/5/7 19:48, Jiri Kosina wrote:
> On Tue, 6 May 2014, Josh Triplett wrote:
> 
>> From 424c7365ed5ed64190a1d08fe30c8e86832368b4 Mon Sep 17 00:00:00 2001
>> From: Josh Triplett <josh@joshtriplett.org>
>> Date: Tue, 6 May 2014 13:20:25 -0700
>> Subject: [PATCH] MAINTAINERS: Add linux-api for review of API/ABI changes
>>
>> 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>
>> ---
>>  MAINTAINERS | 7 +++++++
>>  1 file changed, 7 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7578deb..52a282b 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -210,6 +210,13 @@ S:	Supported
>>  F:	Documentation/scsi/aacraid.txt
>>  F:	drivers/scsi/aacraid/
>>  
>> +ABI/API
>> +L:	linux-api@vger.kernel.org
>> +F:	Documentation/ABI/
>> +F:	include/linux/syscalls.h
>> +F:	include/uapi/
>> +F:	kernel/sys_ni.c
>> +
> 
> It'd be nice to have also sysfs changes covered as well if this is not 
> just about API, but also ABI; I am not sure whether this could be covered 
> by MAINTAINERS pattern, but at least mentioning this list in 
> Documentation/ABI/README seems appropriate.
> 

If sysfs is in, what about cgroupfs? Which has been under dramatic changes.

> (I am also wondering who is actually subsribed to the linux-api@ 
> mailinglist, given the low general awareness of its existance :) ).
> 

Maybe we should force all core deveopers to subscribe linux-api?

  reply	other threads:[~2014-05-08  6:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 17:45 Andy Lutomirski
2014-05-06 17:58 ` josh
2014-05-06 19:12   ` Shuah Khan
2014-05-06 19:16     ` Andy Lutomirski
2014-05-06 19:37       ` Shuah Khan
2014-05-06 19:21   ` Johannes Berg
2014-05-06 19:43     ` Andy Lutomirski
2014-05-06 19:48       ` Johannes Berg
2014-05-06 19:51         ` Andy Lutomirski
2014-05-06 19:45     ` josh
2014-05-06 20:10     ` Daniel Vetter
2014-05-06 20:13       ` Andy Lutomirski
2014-05-07 10:12     ` Laurent Pinchart
2014-05-07 12:36       ` Daniel Vetter
2014-05-07 13:30         ` Laurent Pinchart
2014-05-07 13:50           ` Hans Verkuil
2014-05-12 14:15         ` Wolfram Sang
2014-05-07 17:48   ` Michael Kerrisk (man-pages)
2014-05-06 19:00 ` Greg KH
2014-05-06 20:07   ` Steven Rostedt
2014-05-06 20:34     ` Josh Triplett
2014-05-06 20:42       ` Steven Rostedt
2014-05-06 21:00         ` josh
2014-05-07 11:48       ` Jiri Kosina
2014-05-08  6:35         ` Li Zefan [this message]
2014-05-12  6:37           ` Jiri Kosina
2014-05-07  6:27   ` Michael Kerrisk (man-pages)
2014-05-06 19:57 ` Dan Carpenter
2014-05-08 18:15   ` Randy Dunlap
2014-05-09 11:33 ` Jeff Layton
2014-05-09 11:50   ` Michael Kerrisk (man-pages)

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=536B25AD.8040502@huawei.com \
    --to=lizefan@huawei.com \
    --cc=jkosina@suse.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.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