From: Andi Kleen <ak@suse.de>
To: "Dave Young" <hidave.darkstar@gmail.com>
Subject: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
Date: Thu, 22 Nov 2007 19:19:10 +0100
User-Agent: KMail/1.9.1
Cc: "Rusty Russell" <rusty@rustcorp.com.au>, netdev@vger.kernel.org,
       linux-kernel@vger.kernel.org, sam@ravnborg.org
References: <20071122343.446909000@suse.de> <200711221456.22297.rusty@rustcorp.com.au> <a8e1da0711220041v3d3c27d2pf7f326185666420d@mail.gmail.com>
In-Reply-To: <a8e1da0711220041v3d3c27d2pf7f326185666420d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200711221919.11071.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 591
Lines: 17


> 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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/