From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: [PATCH -next] nfc: shdlc needs to select CRC_CCITT
Date: Mon, 14 May 2012 13:13:25 -0700 [thread overview]
Message-ID: <4FB16765.3090602@xenotime.net> (raw)
In-Reply-To: <20120514200357.e7448e4ca061c8efe3d4757d@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime.net>
Fix build error: SHDLC uses crc_ccitt so it should select CRC_CCITT.
ERROR: "crc_ccitt" [net/nfc/hci/hci.ko] undefined!
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Cc: Lauro Ramos Venancio <lauro.venancio@openbossa.org>
Cc: Aloisio Almeida Jr <aloisio.almeida@openbossa.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>
---
net/nfc/hci/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20120514.orig/net/nfc/hci/Kconfig
+++ linux-next-20120514/net/nfc/hci/Kconfig
@@ -11,6 +11,7 @@ config NFC_SHDLC
depends on NFC_HCI
bool "SHDLC link layer for HCI based NFC drivers"
default n
+ select CRC_CCITT
---help---
Say yes if you use an NFC HCI driver that requires SHDLC link layer.
If unsure, say N here.
next prev parent reply other threads:[~2012-05-14 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 10:03 linux-next: Tree for May 14 Stephen Rothwell
2012-05-14 20:13 ` Randy Dunlap [this message]
2012-05-14 20:32 ` [PATCH -next] nfc: shdlc needs to select CRC_CCITT Samuel Ortiz
2012-05-14 20:14 ` [PATCH -next] wdt: ie6xx_wdt needs io.h Randy Dunlap
2012-05-17 7:11 ` Wim Van Sebroeck
2012-05-14 20:15 ` [PATCH -next] wdt: fix iTCO printk format warnings Randy Dunlap
2012-05-17 7:14 ` Wim Van Sebroeck
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=4FB16765.3090602@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=aloisio.almeida@openbossa.org \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.com \
--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 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).