From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4207F396.7080408@nortel.com> Date: Mon, 07 Feb 2005 17:02:46 -0600 From: Chris Friesen MIME-Version: 1.0 To: Benjamin Herrenschmidt References: <41FECA18.50609@nortelnetworks.com> <1107243398.4208.47.camel@laptopd505.fenrus.org> <41FFA21C.8060203@nortelnetworks.com> <1107273017.4208.132.camel@laptopd505.fenrus.org> <20050204203050.GA5889@dmt.cnet> <4203D793.1040604@nortel.com> <1107595148.30302.5.camel@gaston> <42077EE0.2060505@nortel.com> <1107812101.7734.42.camel@gaston> In-Reply-To: <1107812101.7734.42.camel@gaston> Content-Type: text/plain; charset=us-ascii; format=flowed Cc: linuxppc64-dev , Arjan van de Ven , Linux Kernel list , linuxppc-dev list Subject: Re: question on symbol exports List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Benjamin Herrenschmidt wrote: > Interesting... more than no swap, you must also make sure you have no > r/w mmap'ed file (which are technically equivalent to swap). Ah...thanks for the warning. We want to eventually make it work with swap as well, but that's substantially more complicated. > I'm not too fan about exporting those symbols, but I'll talk to paulus, > it should be possible at least to EXPORT_SYMBOL_GPL them... I understand the reluctance. I'm perfectly willing to export it GPL in my private branch as long as you guys don't consider it evil--the module is going to be GPL anyways. The alternative would be for me to build my code directly in to the kernel...just makes it harder for me to debug. Chris