Linux bluetooth development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	linux-bluetooth@vger.kernel.org,
	Gustavo Padovan <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: [PATCH] Bluetooth: make sure 6LOWPAN_IPHC is built-in if needed
Date: Thu, 13 Mar 2014 11:50:59 +0100	[thread overview]
Message-ID: <20140313105057.GA3596@omega> (raw)
In-Reply-To: <23264195.jQigvx9V9i@wuerfel>

Hi Arnd,

On Thu, Mar 13, 2014 at 11:31:41AM +0100, Arnd Bergmann wrote:
> From 5c094e2f8e556b27a73607fc39d33944c1ec3384 Mon Sep 17 00:00:00 2001
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Thu, 13 Mar 2014 11:27:21 +0100
> Subject: [PATCH] Bluetooth: make sure 6LOWPAN_IPHC is built-in if needed
> 
> Commit 975508879 "Bluetooth: make bluetooth 6lowpan as an option"
> ensures that 6LOWPAN_IPHC is turned on when we have BT_6LOWPAN
> enabled in Kconfig, but it allows building the IPHC code as
> a loadable module even if the entire Bluetooth stack is built-in,
> and that causes a link error.

how do you get this link error? I don't see any linking error.

But I know what you mean, because we have a bool and not a tristate
here and then 6LOWPAN_IPHC is always built-in.

Thanks for fixing this.

- Alex

  reply	other threads:[~2014-03-13 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 10:31 [PATCH] Bluetooth: make sure 6LOWPAN_IPHC is built-in if needed Arnd Bergmann
2014-03-13 10:50 ` Alexander Aring [this message]
2014-03-13 14:07 ` Marcel Holtmann

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=20140313105057.GA3596@omega \
    --to=alex.aring@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@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