[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200711281227.50136.rusty@rustcorp.com.au>
Date: Wed, 28 Nov 2007 12:27:49 +1100
From: Rusty Russell <rusty@...tcorp.com.au>
To: Tom Tucker <tom@...ngridcomputing.com>
Cc: Roland Dreier <rdreier@...co.com>, Andi Kleen <ak@...e.de>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
sam@...nborg.org
Subject: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
On Tuesday 27 November 2007 16:35:42 Tom Tucker wrote:
> On Tue, 2007-11-27 at 15:49 +1100, Rusty Russell wrote:
> Explicitly documenting what comprises the kernel API (external,
> supported) and what comprises the kernel implementation (internal, not
> supported).
But the former is currently an empty set.
> - making it obvious to developers when they are binding their
> implementation to a particular kernel release
See, there's your problem. All interfaces can, and will, change. You're
always binding yourself to a particular release.
So you're not proposing we mark what's not stable, you're arguing that we
create a subset which is stable.
That's an argument we're not (yet) having.
Cheers,
Rusty.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists