From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro. Date: Thu, 22 Nov 2007 19:19:10 +0100 Message-ID: <200711221919.11071.ak@suse.de> References: <20071122343.446909000@suse.de> <200711221456.22297.rusty@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: "Rusty Russell" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, sam@ravnborg.org To: "Dave Young" Return-path: Received: from ns2.suse.de ([195.135.220.15]:60395 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752064AbXKVSXj (ORCPT ); Thu, 22 Nov 2007 13:23:39 -0500 In-Reply-To: Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org > 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