From: Alexander Beregalov <a.beregalov@gmail.com>
To: marcel@holtmann.org, linux-next@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org,
Alexander Beregalov <a.beregalov@gmail.com>
Subject: [PATCH] Bluetooth: depends on RFKILL
Date: Tue, 9 Jun 2009 19:07:40 +0400 [thread overview]
Message-ID: <1244560060-28112-1-git-send-email-a.beregalov@gmail.com> (raw)
Since commit "Bluetooth: Add native RFKILL soft-switch support for all
devices" (611b30f74b5) bluetooth depends on RFKILL.
Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---
net/bluetooth/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig
index 7725da9..85ec71d 100644
--- a/net/bluetooth/Kconfig
+++ b/net/bluetooth/Kconfig
@@ -3,7 +3,7 @@
#
menuconfig BT
- depends on NET && !S390
+ depends on NET && RFKILL && !S390
tristate "Bluetooth subsystem support"
help
Bluetooth is low-cost, low-power, short-range wireless technology.
--
1.6.3.1
next reply other threads:[~2009-06-09 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:07 Alexander Beregalov [this message]
2009-06-09 15:22 ` [PATCH] Bluetooth: depends on RFKILL Marcel Holtmann
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=1244560060-28112-1-git-send-email-a.beregalov@gmail.com \
--to=a.beregalov@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcel@holtmann.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