[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8e1da0711221806r5bc80cfchfa65b96a37d6d20a@mail.gmail.com>
Date: Fri, 23 Nov 2007 10:06:58 +0800
From: "Dave Young" <hidave.darkstar@...il.com>
To: "Andi Kleen" <ak@...e.de>
Cc: "Rusty Russell" <rusty@...tcorp.com.au>, 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 Nov 23, 2007 2:19 AM, Andi Kleen <ak@...e.de> wrote:
>
> > Andy, I like your idea. IMHO, as Rusty said a simple EXPORT_SYMBOL_TO
> > is better.
>
> I don't think so. e.g. tcpcong would be very very messy this way.
>
> > And I wonder if it is possible to export to something like the struct
> > device_driver? If it's possible then it will not limited to modules.
>
> Not sure I follow you. Can you expand?
>
I know little about module internal, so if I'm wrong please just don't
mind, please point out or just ignore.
Kernel symbols could apply to kernel object model, doesn't it?
I just think that because the device_driver have a mod_name member
(for built-in module), so if something can be done as device driver is
registered.
-
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