From: Gustavo Padovan <padovan-Y3ZbgMPKUGA34EUeqzHoZw@public•gmane.org>
To: Andrei Emeltchenko
<andrei.emeltchenko.news-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>,
Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public•gmane.org>,
Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
LKML <linux-kernel@vg>
Subject: Re: linux-next: Tree for Nov 17 (bluetooth)
Date: Fri, 18 Nov 2011 11:30:17 -0200 [thread overview]
Message-ID: <20111118133017.GA2131@joana> (raw)
In-Reply-To: <20111118095855.GB9034@aemeltch-MOBL1>
Hi Andrei,
* Andrei Emeltchenko <andrei.emeltchenko.news-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org> [2011-11-18 11:58:58 +0200]:
> Hi Randy,
>
> On Thu, Nov 17, 2011 at 09:50:39AM -0800, Randy Dunlap wrote:
> > On 11/16/2011 08:07 PM, Stephen Rothwell wrote:
> > > Hi all,
> >
> >
> > When CONFIG_BT_L2CAP is not enabled:
> >
> > net/built-in.o: In function `hci_dev_open':
> > (.text+0xdce9a): undefined reference to `enable_hs'
>
> Despite not enabling L2CAP sounds strange we might find solution even for
> this usage :-)
> I am thinking about moving enable_hs to common part not depending on
> CONFIG_BT_L2CAP option:
This is ok, please send a proper git patch so I can apply it.
Gustavo
next prev parent reply other threads:[~2011-11-18 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 4:07 linux-next: Tree for Nov 17 Stephen Rothwell
2011-11-17 12:00 ` Alan Cox
2011-11-17 17:50 ` linux-next: Tree for Nov 17 (bluetooth) Randy Dunlap
2011-11-18 9:58 ` Andrei Emeltchenko
2011-11-18 13:30 ` Gustavo Padovan [this message]
2011-11-18 13:41 ` Andrei Emeltchenko
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=20111118133017.GA2131@joana \
--to=padovan-y3zbgmpkuga34eueqzhozw@public$(echo .)gmane.org \
--cc=andrei.emeltchenko.news-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=linux-kernel@vg \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public$(echo .)gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public$(echo .)gmane.org \
/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