From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753709AbYLAUN1 (ORCPT ); Mon, 1 Dec 2008 15:13:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752529AbYLAUNQ (ORCPT ); Mon, 1 Dec 2008 15:13:16 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:57177 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751763AbYLAUNP (ORCPT ); Mon, 1 Dec 2008 15:13:15 -0500 Date: Mon, 1 Dec 2008 12:12:12 -0800 (PST) From: Linus Torvalds To: Pekka Enberg cc: Andrew Morton , Matt Mackall , 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 In-Reply-To: <84144f020812011207q29fe4b3fq11a9e55f171cf743@mail.gmail.com> Message-ID: References: <1227980689.6354.24.camel@localhost.localdomain> <20081129214207.GA6747@x200.localdomain> <20081129234907.GA2340@kroah.com> <20081201101245.0a2f3123.randy.dunlap@oracle.com> <1228158811.3196.88.camel@calx> <20081201120210.1ed16bd5.akpm@linux-foundation.org> <84144f020812011207q29fe4b3fq11a9e55f171cf743@mail.gmail.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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