From: Linus Torvalds <torvalds@linux-foundation.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matt Mackall <mpm@selenic.com>,
randy.dunlap@oracle.com, greg@kroah.com, adobriyan@gmail.com,
remi.colinet@gmail.com, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RESEND][PATCH] Add /proc/mempool to display mempool usage
Date: Mon, 1 Dec 2008 12:12:12 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812011210030.3256@nehalem.linux-foundation.org> (raw)
In-Reply-To: <84144f020812011207q29fe4b3fq11a9e55f171cf743@mail.gmail.com>
On Mon, 1 Dec 2008, Pekka Enberg wrote:
>
> Hmm, I thought Documentation/ABI/ was supposed to tell us what's an
> ABI you can depend on and what's not. I mean, you shouldn't be
> depending on anything but the interfaces documented in
> Documentation/ABI/stable/, no?
Who is the f*cking MORON that thinks that "documentation" has any meaning
what-so-ever?
The fact that something is documented (whether correctly or not) has
absolutely _zero_ impact on anything at all. What makes something an ABI
is that it's useful and available. The only way something isn't an ABI is
by _explicitly_ making sure that it's not available even by mistake in a
stable form for binary use.
Example: kernel internal data structures and function calls. We make sure
that you simply _cannot_ make a binary that works across kernel versions.
That is the only way for an ABI to not form.
Linus
next prev parent reply other threads:[~2008-12-01 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 17:44 Remi Colinet
2008-11-29 21:42 ` Alexey Dobriyan
2008-11-29 23:49 ` Greg KH
2008-11-30 21:00 ` Remi Colinet
2008-12-01 18:12 ` Randy Dunlap
2008-12-01 19:13 ` Matt Mackall
2008-12-01 20:02 ` Andrew Morton
2008-12-01 20:07 ` Pekka Enberg
2008-12-01 20:12 ` Linus Torvalds [this message]
2008-12-01 20:23 ` Linus Torvalds
2008-12-01 22:02 ` Pekka Enberg
2008-12-01 22:20 ` Matt Mackall
2008-12-02 2:54 ` Linus Torvalds
2008-12-04 16:02 ` Michael Kerrisk
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=alpine.LFD.2.00.0812011210030.3256@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
--cc=randy.dunlap@oracle.com \
--cc=remi.colinet@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
Powered by JetHome