From: David Herrmann <dh.herrmann@googlemail.com>
To: linux-input@vger.kernel.org
Cc: rdunlap@xenotime.net, linux-next@vger.kernel.org,
jkosina@suse.cz, linux-kernel@vger.kernel.org,
David Herrmann <dh.herrmann@googlemail.com>
Subject: [PATCH] HID: wiimote: Select INPUT_FF_MEMLESS
Date: Wed, 7 Dec 2011 21:33:59 +0100 [thread overview]
Message-ID: <1323290039-28073-1-git-send-email-dh.herrmann@googlemail.com> (raw)
In-Reply-To: <4EDFD23D.4030703@xenotime.net>
We depend on memless force-feedback support, therefore correctly select the
related config options.
Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
---
Hi Randy
Thanks for reporting this. This patch should fix this. I don't know whether such
fixes belong to stable tree, if they do, Jiri could you CC stable when applying
it?
Cheers
David
drivers/hid/Kconfig | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
index edf2b2b..dae04a0 100644
--- a/drivers/hid/Kconfig
+++ b/drivers/hid/Kconfig
@@ -591,6 +591,7 @@ config HID_WIIMOTE
depends on BT_HIDP
depends on LEDS_CLASS
select POWER_SUPPLY
+ select INPUT_FF_MEMLESS
---help---
Support for the Nintendo Wii Remote bluetooth device.
--
1.7.8
next prev parent reply other threads:[~2011-12-07 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 6:12 linux-next: Tree for Dec 7 Stephen Rothwell
2011-12-07 10:39 ` Sasha Levin
2011-12-07 19:59 ` Sasha Levin
2011-12-07 19:10 ` linux-next: Tree for Dec 7 (x86, not SMP) Randy Dunlap
2011-12-07 19:42 ` Don Zickus
2011-12-07 20:43 ` Randy Dunlap
2011-12-07 21:06 ` Don Zickus
2011-12-08 2:45 ` Randy Dunlap
2011-12-07 20:41 ` linux-next: Tree for Dec 7 (kvm) Randy Dunlap
2011-12-07 20:53 ` linux-next: Tree for Dec 7 (hid/hid-wiimote) Randy Dunlap
2011-12-07 20:33 ` David Herrmann [this message]
2011-12-07 21:07 ` [PATCH] HID: wiimote: Select INPUT_FF_MEMLESS simon
2011-12-08 8:31 ` David Herrmann
2011-12-08 16:23 ` simon
2011-12-08 22:43 ` Sean Young
2011-12-07 21:51 ` Randy Dunlap
2011-12-11 23:27 ` Jiri Kosina
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=1323290039-28073-1-git-send-email-dh.herrmann@googlemail.com \
--to=dh.herrmann@googlemail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for NNTP newsgroup(s).