From: Adrian Bunk <bunk@stusta.de>
To: marcel@holtmann.org, maxk@qualcomm.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bluez-devel@lists.sf.net, linux390@de.ibm.com
Subject: [2.6 patch] let BT_HIDP depend on INPUT
Date: Mon, 10 Jul 2006 20:31:54 +0200 [thread overview]
Message-ID: <20060710183154.GD13938@stusta.de> (raw)
This patch let's BT_HIDP depend on instead of select INPUT.
This fixes the following warning during an s390 build:
<-- snip -->
...
net/bluetooth/hidp/Kconfig:4:warning: 'select' used by config symbol 'BT_HIDP' refer to undefined symbol 'INPUT'
...
<-- snip -->
A dependency on INPUT also implies !S390 (and therefore makes the
explicit dependency obsolete) since INPUT is not available on s390.
The practical difference should be nearly zero, since INPUT is always
set to y unless EMBEDDED=y (or S390=y).
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.18-rc1-mm1-full/net/bluetooth/hidp/Kconfig.old 2006-07-10 16:51:59.000000000 +0200
+++ linux-2.6.18-rc1-mm1-full/net/bluetooth/hidp/Kconfig 2006-07-10 16:52:52.000000000 +0200
@@ -1,7 +1,6 @@
config BT_HIDP
tristate "HIDP protocol support"
- depends on BT && BT_L2CAP && (BROKEN || !S390)
- select INPUT
+ depends on INPUT && BT && BT_L2CAP
help
HIDP (Human Interface Device Protocol) is a transport layer
for HID reports. HIDP is required for the Bluetooth Human
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-07-10 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 18:31 Adrian Bunk [this message]
2006-07-10 19:07 ` [2.6 patch] let BT_HIDP depend on INPUT Marcel Holtmann
2006-07-10 19:33 ` Adrian Bunk
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=20060710183154.GD13938@stusta.de \
--to=bunk@stusta.de \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).