From: Rob Landley <rob@landley.net>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tao Ma <boyu.mt@taobao.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Documentation/ABI: Document the non-ABI status of Kconfig and symbols
Date: Sun, 10 Nov 2013 16:03:29 -0600 [thread overview]
Message-ID: <1384121009.1974.263@driftwood> (raw)
In-Reply-To: <20131024090825.GA3217@leaf> (from josh@joshtriplett.org on Thu Oct 24 04:08:30 2013)
On 10/24/2013 04:08:30 AM, Josh Triplett wrote:
> On Thu, Oct 24, 2013 at 10:57:11AM +0200, Richard Weinberger wrote:
> > On Thu, Oct 24, 2013 at 10:41 AM, Josh Triplett
> <josh@joshtriplett.org> wrote:
> > > Discussion at Kernel Summit made it clear that the presence or
> absence
> > > of specific Kconfig symbols are not considered ABI, and that no
> > > userspace (or bootloader, etc) should rely on them.
> > >
> > > In addition, kernel-internal symbols are well established as
> non-ABI,
> > > per Documentation/stable_api_nonsense.txt.
> > >
> > > Document both of these in Documentation/ABI/README, in a new
> section for
> > > notable bits of non-ABI.
> > >
> > > Signed-off-by: Josh Triplett <josh@joshtriplett.org>
> > > ---
> > > Documentation/ABI/README | 13 +++++++++++++
> > > 1 file changed, 13 insertions(+)
Should I grab this, or is it already going in through somebody else's
tree?
Rob
next prev parent reply other threads:[~2013-11-10 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 8:41 [PATCH] Documentation/ABI: Document the non-ABI status of Kconfig and symbols Josh Triplett
2013-10-24 8:44 ` H. Peter Anvin
2013-10-24 8:57 ` Richard Weinberger
2013-10-24 9:08 ` Josh Triplett
2013-11-10 22:03 ` Rob Landley [this message]
2013-10-25 15:06 ` H. Peter Anvin
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=1384121009.1974.263@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=boyu.mt@taobao.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=torvalds@linux-foundation.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