Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756848AbYGAN1X (ORCPT ); Tue, 1 Jul 2008 09:27:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755021AbYGAN1J (ORCPT ); Tue, 1 Jul 2008 09:27:09 -0400 Received: from wx-out-0506.google.com ([66.249.82.228]:49579 "EHLO wx-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753642AbYGAN1H (ORCPT ); Tue, 1 Jul 2008 09:27:07 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=h19MHlCDQdWJ9abixGmMS2MaTGaGqLTHft7BhBPInNiaVmWMmFLb9er56qNBDe9abm uINkiLoW/mdOkpnDaTAFjHABE3dILuYoOCdiAsThh2UUdHv9XpXXho/TQvpdUMposPT8 ofp5gPy2T0mwCE/spd21PonYO+2yVxURzNtXM= Date: Tue, 1 Jul 2008 09:27:02 -0400 From: Dmitry Torokhov To: Adrian Bunk Cc: Geert Uytterhoeven , Linus Torvalds , Andrew Morton , linux-input@vger.kernel.org, Linux Kernel Development , Linux/m68k Subject: Re: [PATCH] drivers/input/ff-core.c needs Message-ID: <20080701092542.ZZRA012@mailhub.coreip.homeip.net> References: <20080701084316.ZZRA012@mailhub.coreip.homeip.net> <20080701130517.GA29863@cs181140183.pp.htv.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080701130517.GA29863@cs181140183.pp.htv.fi> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2549 Lines: 57 On Tue, Jul 01, 2008 at 04:05:17PM +0300, Adrian Bunk wrote: > On Tue, Jul 01, 2008 at 08:46:54AM -0400, Dmitry Torokhov wrote: > > On Tue, Jul 01, 2008 at 01:55:25PM +0200, Geert Uytterhoeven wrote: > > > commit 656acd2bbc4ce7f224de499ee255698701396c48 > > > Author: Dmitry Torokhov > > > Date: Thu Jun 26 11:30:02 2008 -0400 > > > > > > Input: fix locking in force-feedback core > > > > > > The newly added event_lock spinlock in the input core disallows sleeping > > > and therefore using mutexes in event handlers. Convert force-feedback > > > core to rely on event_lock instead of mutex to protect slots allocated > > > for fore-feedback effects. The original mutex is still used to serialize > > > uploading and erasing of effects. > > > > > > causes the following regression on m68k: > > > > > > | linux/drivers/input/ff-core.c: In function 'input_ff_upload': > > > | linux/drivers/input/ff-core.c:172: error: dereferencing pointer to incomplete type > > > | linux/drivers/input/ff-core.c: In function 'erase_effect': > > > | linux/drivers/input/ff-core.c:197: error: dereferencing pointer to incomplete type > > > | linux/drivers/input/ff-core.c:204: error: dereferencing pointer to incomplete type > > > | make[4]: *** [drivers/input/ff-core.o] Error 1 > > > > > > > Argh! Sorry about it. > > > > > As the incomplete type is `struct task_struct', including fixes > > > it. > > > > Not linux/spinlock.h? I wonder if I need to include linux/spinlock.h and > > linux/mutex.h directly from linux/input.h... What is the current > > policy on headers - do they need to include everything to be > > functional or it is responsibility of the user? > > Theoretically it's the responsibility of the header to include > everything it needs. > > In practice we are after -rc8 and even thinking of this kind of #include > changes under include/linux/ makes me nervous - like the fact that the > ff-core.c problem occured _only_ on m68k our headers are too fragile for > expecting such changes to simply work. > > Can we go with Geert's patch for 2.6.26 and if you want to fix it > properly you can send a patch for 2.6.27? > No, no, I am totally fine with Geert's fix, I am talking about later of course. -- Dmitry -- 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/