From: Johannes Berg <johannes@sipsolutions•net>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
marcel@holtmann•org
Subject: Re: linux-next: Tree for June 11 (bluetooth/rfkill)
Date: Fri, 12 Jun 2009 14:12:06 +0200 [thread overview]
Message-ID: <1244808726.29447.11.camel@johannes.local> (raw)
In-Reply-To: <4A318519.2080708@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Thu, 2009-06-11 at 15:28 -0700, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20090610:
>
>
> CONFIG_RFKILL=m
> CONFIG_BT=y
>
> (.text+0xb7bf7): undefined reference to `rfkill_unregister'
> (.text+0xb7c03): undefined reference to `rfkill_destroy'
> (.text+0xb962f): undefined reference to `rfkill_blocked'
> (.text+0xba173): undefined reference to `rfkill_alloc'
> (.text+0xba187): undefined reference to `rfkill_register'
> (.text+0xba197): undefined reference to `rfkill_destroy'
This one's not my fault :) Marcel did that, the solution as usual is to
depends on RFKILL || !RFKILL
:)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-06-12 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 9:14 linux-next: Tree for June 11 Stephen Rothwell
2009-06-11 22:21 ` linux-next: Tree for June 11 (cnic) Randy Dunlap
2009-06-18 10:16 ` Kamalesh Babulal
2009-06-11 22:28 ` linux-next: Tree for June 11 (bluetooth/rfkill) Randy Dunlap
2009-06-12 12:12 ` Johannes Berg [this message]
2009-06-11 22:35 ` linux-next: Tree for June 11 (ieee802154) Randy Dunlap
2009-06-12 22:59 ` [PATCH -next] ieee802154: fix kconfig bool/tristate muckup Randy Dunlap
2009-06-13 10:57 ` Sergey Lapin
2009-06-14 6:37 ` David Miller
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=1244808726.29447.11.camel@johannes.local \
--to=johannes@sipsolutions$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marcel@holtmann$(echo .)org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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