From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Marcel Holtmann <marcel@holtmann.org>,
"Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: [PATCH -next] bluetooth: uses crypto interfaces, select CRYPTO
Date: Wed, 22 Jun 2011 10:08:11 -0700 [thread overview]
Message-ID: <20110622100811.258091ff.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110622163651.7ebc407c.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Recent changes to hci_core.c use crypto interfaces, so select CRYPTO
to make sure that those interfaces are present.
Fixes these build errors when CRYPTO is not enabled:
net/built-in.o: In function `hci_register_dev':
(.text+0x4cf86): undefined reference to `crypto_alloc_base'
net/built-in.o: In function `hci_unregister_dev':
(.text+0x4f912): undefined reference to `crypto_destroy_tfm'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
net/bluetooth/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20110622.orig/net/bluetooth/Kconfig
+++ linux-next-20110622/net/bluetooth/Kconfig
@@ -6,6 +6,7 @@ menuconfig BT
tristate "Bluetooth subsystem support"
depends on NET && !S390
depends on RFKILL || !RFKILL
+ select CRYPTO
help
Bluetooth is low-cost, low-power, short-range wireless technology.
It was designed as a replacement for cables and other short-range
next prev parent reply other threads:[~2011-06-22 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 6:36 linux-next: Tree for June 22 Stephen Rothwell
2011-06-22 17:06 ` [PATCH -next] mfd: tps65912 needs MFD_CORE Randy Dunlap
2011-06-22 18:29 ` Mark Brown
2011-06-22 18:46 ` Randy Dunlap
2011-06-22 17:08 ` Randy Dunlap [this message]
2011-06-27 18:03 ` [PATCH -next] bluetooth: uses crypto interfaces, select CRYPTO Randy Dunlap
2011-06-27 18:03 ` Randy Dunlap
2011-06-27 18:13 ` Gustavo F. Padovan
2011-06-27 18:13 ` Gustavo F. Padovan
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=20110622100811.258091ff.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.