mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Howells <dhowells@redhat.com>
Cc: 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 09:30:26 -0800	[thread overview]
Message-ID: <20110307093026.42d62518.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110307113523.24025.37925.stgit@warthog.procyon.org.uk>

On Mon, 07 Mar 2011 11:35:23 +0000 David Howells wrote:

> Add a guideline indicating who to notify about new userspace API/ABI elements,
> such as new system calls or error codes.
> 
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
> 
>  MAINTAINERS |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 560ecce..694bec2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -63,7 +63,10 @@ trivial patch so apply some common sense.
>  	please Cc: security@kernel.org, especially if the maintainer
>  	does not respond.
>  
> -8.	Happy hacking.
> +8.	When adding new userspace API/ABI elements, notably system calls and
> +	error codes, please cc <linux-api@vger.kernel.org>.
> +
> +9.	Happy hacking.
>  
>  Descriptions of section entries:
>  
> 
> --

No objection other than I dislike having the same info in multiple places --
updates get out of sync easily and this is somewhat already in
Documentation/HOWTO and Documentation/SubmitChecklist.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      parent reply	other threads:[~2011-03-07 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 11:35 David Howells
2011-03-07 14:36 ` Joe Perches
2011-03-07 14:43   ` Arnd Bergmann
2011-03-07 14:45 ` David Howells
2011-03-07 17:30 ` Randy Dunlap [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=20110307093026.42d62518.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=dhowells@redhat.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

all inboxes | Powered by JetHome®