[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdUgyDgOttd+VFJviKw=WCNpt7rjEHC_FCNLfujcr-4m4A@mail.gmail.com>
Date: Mon, 6 Feb 2012 11:41:51 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
"Gustavo F. Padovan" <padovan@...fusion.mobi>,
Marcel Holtmann <marcel@...tmann.org>,
"David S. Miller" <davem@...emloft.net>,
linux-bluetooth@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] blutetooth: Remove bogus inline for l2cap_chan_connect()
Hi Johan,
On Sun, Jan 15, 2012 at 12:25, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Sun, Jan 15, 2012 at 11:52, Johan Hedberg <johan.hedberg@...il.com> wrote:
>>> net/bluetooth/l2cap_sock.c: In function ‘l2cap_sock_connect’:
>>> include/net/bluetooth/l2cap.h:838: sorry, unimplemented: inlining failed in call to ‘l2cap_chan_connect’: function body not available
>>> net/bluetooth/l2cap_sock.c:126: sorry, unimplemented: called from here
>>> make[1]: *** [net/bluetooth/l2cap_sock.o] Error 1
>
>> This was already reported[1] earlier this month and a patch[2] was also
>
> Ah, it was reported as a sparse warning. I guess that's why I didn't find it.
> But a build error is worse.
>
>> created for it which right now resides in my bluetooth-next tree[3].
>> [3] http://git.kernel.org/?p=linux/kernel/git/jh/bluetooth-next.git;a=commitdiff;h=cd555072d0b0738c8a107776fe91902da686f94d
This doesn't seem to be in linux-next, as -next pulls
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next.git
instead?
Can we please get the fix in mainline ASAP, as it breaks the build with some
versions of gcc?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists