|| ||Linus Torvalds <torvalds-AT-linux-foundation.org>|
|| ||Pekka Enberg <penberg-AT-cs.helsinki.fi>|
|| ||Re: [RESEND][PATCH] Add /proc/mempool to display mempool usage|
|| ||Mon, 1 Dec 2008 12:12:12 -0800 (PST)|
|| ||Andrew Morton <akpm-AT-linux-foundation.org>,
Matt Mackall <mpm-AT-selenic.com>, randy.dunlap-AT-oracle.com,
greg-AT-kroah.com, adobriyan-AT-gmail.com, remi.colinet-AT-gmail.com,
|| ||Article, Thread
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
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.
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)