public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Joe Perches <joe@perches.com>
Cc: David Howells <dhowells@redhat.com>,
	mtk.manpages@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add a guideline on notification of new userspace API/ABI elements
Date: Mon, 7 Mar 2011 15:43:55 +0100	[thread overview]
Message-ID: <201103071543.56086.arnd@arndb.de> (raw)
In-Reply-To: <1299508603.20104.30.camel@Joe-Laptop>

On Monday 07 March 2011, Joe Perches wrote:
> Hey David.
> 
> Is there some list of files that are more likely to
> trigger this?
> 
> Maybe add a section like:
> 
> USERSPACE ABI/API INTERFACES
> L:      linux-api@vger.kernel.org
> F:      include/asm-generic/errno*.h
> F:      include/linux/capability.h
> F:      include/linux/compat.h
> F:      include/linux/syscalls.h
> F:      include/*/unistd.h

syscalls.h and compat.h are not really the user space ABI,
as user applications don't use those headers to link to
the kernel.

> Maybe add some arch wildcards?
> 
> F:      arch/*/include/asm/errno.h
> F:      arch/*/include/asm/unistd.h
> 
> Maybe add fs?
> 
> F:      fs/compat*.c
> 
> There's probably a bunch of others.
> Suggestions?
> 

I think you can add the entire asm-generic directory. The majority
of the changes in there are to exported files, so they impact
the ABI. For a specific list, you'd have to go through all the
files listed as exported in include/{linux,asm-generic}/Kbuild.

	Arnd

  reply	other threads:[~2011-03-07 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 11:35 [PATCH] MAINTAINERS: Add a guideline on notification of new userspace API/ABI elements David Howells
2011-03-07 14:36 ` Joe Perches
2011-03-07 14:43   ` Arnd Bergmann [this message]
2011-03-07 14:45   ` David Howells
2011-03-07 17:30 ` Randy Dunlap

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=201103071543.56086.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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