Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.

> 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? 

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
  - From: "Dave Young" <[email protected]>

References:
- [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
  - From: Andi Kleen <[email protected]>
- Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
  - From: Rusty Russell <[email protected]>
- Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
  - From: "Dave Young" <[email protected]>

Prev by Date: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
Next by Date: Re: Why is FIBMAP ioctl root only?
Previous by thread: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
Next by thread: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]