From: Randy Dunlap <randy.dunlap@oracle.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
platform-driver-x86@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Daniel Oliveira Nascimento <don@syst.com.br>
Subject: Re: [PATCH -next] classmate-laptop: fix for RFKILL=m, CMPC=y
Date: Wed, 09 Jun 2010 13:05:04 -0700 [thread overview]
Message-ID: <4C0FF3F0.2080601@oracle.com> (raw)
In-Reply-To: <20100609200218.GD2551@barata.holoscopio.com>
On 06/09/10 13:02, Thadeu Lima de Souza Cascardo wrote:
> On Thu, Jun 03, 2010 at 09:39:03AM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Fix build error when CONFIG_RFKILL=m and CONFIG_ACPI_CMPC=y:
>> classmate-laptop should depend on RFKILL or RFKILL=n.
>>
>> classmate-laptop.c:(.text+0x1351fc): undefined reference to `rfkill_unregister'
>> classmate-laptop.c:(.text+0x135204): undefined reference to `rfkill_destroy'
>> classmate-laptop.c:(.text+0x135237): undefined reference to `rfkill_set_sw_state'
>> classmate-laptop.c:(.text+0x1352b9): undefined reference to `rfkill_alloc'
>> classmate-laptop.c:(.text+0x1352ca): undefined reference to `rfkill_register'
>> classmate-laptop.c:(.text+0x1352d6): undefined reference to `rfkill_destroy'
>>
>> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
>> ---
>
>
> Randy,
>
> Since this implies a build failure, shouldn't it be sent for rc too?
Yes, it should.
I hit the problem during a linux-next build, but it does apply to mainline as well.
Thanks.
>> drivers/platform/x86/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> --- linux-next-20100603.orig/drivers/platform/x86/Kconfig
>> +++ linux-next-20100603/drivers/platform/x86/Kconfig
>> @@ -520,6 +520,7 @@ config TOSHIBA_BT_RFKILL
>> config ACPI_CMPC
>> tristate "CMPC Laptop Extras"
>> depends on X86 && ACPI
>> + depends on RFKILL || RFKILL=n
>> select INPUT
>> select BACKLIGHT_CLASS_DEVICE
>> default n
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-06-09 20:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 3:47 linux-next: Tree for June 3 Stephen Rothwell
2010-06-03 7:39 ` Dave Young
2010-06-03 8:00 ` Dave Young
2010-06-03 8:16 ` Dave Young
2010-06-03 12:52 ` Rusty Russell
2010-06-04 19:46 ` Tony Luck
2010-06-04 20:04 ` Linus Torvalds
2010-06-04 20:46 ` Luck, Tony
2010-06-04 22:05 ` Linus Torvalds
2010-06-04 22:50 ` Luck, Tony
2010-06-04 22:57 ` Linus Torvalds
2010-06-05 2:39 ` Rusty Russell
2010-06-05 2:51 ` Rusty Russell
2010-06-05 4:01 ` Rusty Russell
2010-06-07 18:16 ` Luck, Tony
2010-06-03 15:46 ` linux-next: Tree for June 3 (qlcnic) Randy Dunlap
2010-06-03 17:31 ` Anirban Chakraborty
2010-06-03 15:55 ` linux-next: Tree for June 3 (iwlwifi) Randy Dunlap
2010-06-03 17:21 ` John W. Linville
2010-06-03 17:42 ` Guy, Wey-Yi
2010-06-03 17:45 ` reinette chatre
2010-06-03 16:39 ` [PATCH -next] classmate-laptop: fix for RFKILL=m, CMPC=y Randy Dunlap
2010-06-09 20:02 ` Thadeu Lima de Souza Cascardo
2010-06-09 20:05 ` Randy Dunlap [this message]
2010-06-09 20:11 ` Matthew Garrett
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=4C0FF3F0.2080601@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=cascardo@holoscopio.com \
--cc=don@syst.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--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