Linux wireless drivers development
 help / color / mirror / Atom feed
From: Samuel Ortiz <samuel@sortiz.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] NFC: Add missing RFKILL dependency for Kconfig
Date: Sat, 27 Apr 2013 01:19:24 +0200	[thread overview]
Message-ID: <1367018364.32385.3.camel@zurbaran> (raw)
In-Reply-To: <1366999114-26903-1-git-send-email-marcel@holtmann.org>

Hi Marcel,

On Fri, 2013-04-26 at 10:58 -0700, Marcel Holtmann wrote:
> Since the NFC subsystem gained RFKILL support, it needs to be able
> to build properly with whatever option for RFKILL has been selected.
> 
> on i386:
> 
> net/built-in.o: In function `nfc_unregister_device':
> (.text+0x6a36d): undefined reference to `rfkill_unregister'
> net/built-in.o: In function `nfc_unregister_device':
> (.text+0x6a378): undefined reference to `rfkill_destroy'
> net/built-in.o: In function `nfc_register_device':
> (.text+0x6a493): undefined reference to `rfkill_alloc'
> net/built-in.o: In function `nfc_register_device':
> (.text+0x6a4a4): undefined reference to `rfkill_register'
> net/built-in.o: In function `nfc_register_device':
> (.text+0x6a4b3): undefined reference to `rfkill_destroy'
> net/built-in.o: In function `nfc_dev_up':
> (.text+0x6a8e8): undefined reference to `rfkill_blocked'
> 
> when CONFIG_RFKILL=m but NFC is builtin.
> 
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>  net/nfc/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
Applied to nfc-next, thanks.

Cheers,
Samuel.




      parent reply	other threads:[~2013-04-26 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 17:58 [PATCH] NFC: Add missing RFKILL dependency for Kconfig Marcel Holtmann
2013-04-26 18:06 ` Randy Dunlap
2013-04-26 23:19 ` Samuel Ortiz [this message]

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=1367018364.32385.3.camel@zurbaran \
    --to=samuel@sortiz.org \
    --cc=linux-wireless@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