From: Adrian Bunk <bunk@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] drivers/input/ff-core.c needs <linux/sched.h>
Date: Tue, 1 Jul 2008 16:05:17 +0300 [thread overview]
Message-ID: <20080701130517.GA29863@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20080701084316.ZZRA012@mailhub.coreip.homeip.net>
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 <dmitry.torokhov@gmail.com>
> > 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 <linux/sched.h> 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?
> Dmitry
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-07-01 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 11:55 Geert Uytterhoeven
2008-07-01 12:46 ` Dmitry Torokhov
2008-07-01 13:05 ` Adrian Bunk [this message]
2008-07-01 13:14 ` Geert Uytterhoeven
2008-07-01 13:27 ` Dmitry Torokhov
2008-07-02 20:43 ` Dmitry Torokhov
2008-07-03 1:39 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080701130517.GA29863@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®