From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <45A2C693.2000402@xmission.com> Date: Mon, 08 Jan 2007 15:32:51 -0700 From: Brad Midgley MIME-Version: 1.0 To: BlueZ development References: <20070108143727.5d5f9b01@ningauble.scrye.com> In-Reply-To: <20070108143727.5d5f9b01@ningauble.scrye.com> Subject: Re: [Bluez-devel] 2 plugz issues Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Kevin > If this patch is needed, is there any move to get it pushed to > upstream? One of the reasons I was very happy about this new setup was > that I didn't need to compile an out of tree module with every kernel > update, but now it's worse if I have to make a new kernel with this > patch. ;( yes that is the idea. Fabien has been adapting it according to Marcel's feedback but ultimately Marcel needs to give it the nod. Brad ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel