[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071127155828.GF24223@one.firstfloor.org>
Date: Tue, 27 Nov 2007 16:58:28 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Jonathan Corbet <corbet@....net>
Cc: Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@...e.de>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
sam@...nborg.org, Roland Dreier <rdreier@...co.com>
Subject: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
On Tue, Nov 27, 2007 at 08:43:24AM -0700, Jonathan Corbet wrote:
> Rusty said:
>
> > Well, introduce an EXPORT_SYMBOL_INTERNAL(). It's a lot less code. But you'd
> > still need to show that people are having trouble knowing what APIs to use.
>
> Might the recent discussion on the exporting of sys_open() and
> sys_read() be an example here? There would appear to be a consensus
> that people should not have used those functions, but they are now
> proving difficult to unexport.
That is a good example yes.
> Perhaps the best use of the namespace stuff might be for *future*
> exports which are needed to help make the mainline kernel fully modular,
> but which are not meant to be part of a more widely-used API?
Not sure about future only, but yes that is its intention.
Thanks for putting it clearly.
-Andi
-
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