Re: linux-next: build failure after merge of the bluetooth tree

Hi Luiz, On Thu, 8 Apr 2021 04:47:04 + "Von Dentz, Luiz" wrote: > > I'd leave this for Marcel to comments, but there are quite many > instances of // comment like that, so I wonder what is going on, or > perhaps that is not allowed in include/uapi? We only do these standalone compile

linux-next: build failure after merge of the bluetooth tree

Hi all, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from :32: ./usr/include/linux/virtio_bt.h:1:1: error: C++ style comments are not allowed in ISO C90 1 | // SPDX-License-Identifier: BSD-3-Clause | ^

Re: linux-next: build failure after merge of the bluetooth tree

Same here, thanks for the fix! On Mon, Jul 27, 2020 at 1:22 AM Christoph Hellwig wrote: > > The fixup looks good to me, thanks.

Re: linux-next: build failure after merge of the bluetooth tree

The fixup looks good to me, thanks.

linux-next: build failure after merge of the bluetooth tree

Hi all, After merging the bluetooth tree, today's linux-next build (arm multi_v7_defconfig) failed like this: net/bluetooth/sco.c: In function 'sco_sock_setsockopt': net/bluetooth/sco.c:862:3: error: cannot convert to a pointer type 862 | if (get_user(opt, (u32 __user *)optval)) { |

linux-next: build failure after merge of the bluetooth tree

Hi all, After merging the bluetooth tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from drivers/bluetooth/hci_ldisc.c:34: drivers/bluetooth/btintel.h: In function 'btintel_reset_to_bootloader': drivers/bluetooth/btintel.h:188:9: warning: 'return' with

Re: linux-next: build failure after merge of the bluetooth tree

From: Stephen Rothwell Date: Tue, 22 Sep 2015 11:20:15 +1000 > From: Stephen Rothwell > Subject: drivers/net/ieee802154/at86rf230.c: seq_printf() now returns NULL > > Signed-off-by: Stephen Rothwell > Cc: Alexander Aring > Cc: Stefan Schmidt > Cc: Marcel Holtmann > Signed-off-by: Andrew

Re: linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, On Mon, 14 Sep 2015 10:22:34 +1000 Stephen Rothwell wrote: > > On Mon, 14 Sep 2015 10:14:28 +1000 Stephen Rothwell > wrote: > > > > I applied the patches that Andrew has had in his post merge series > > (but I think you were sent a rolled up version): > > Actually it was sent by

Re: linux-next: build failure after merge of the bluetooth tree

From: Stephen Rothwell Date: Tue, 22 Sep 2015 11:20:15 +1000 > From: Stephen Rothwell > Subject: drivers/net/ieee802154/at86rf230.c: seq_printf() now returns NULL > > Signed-off-by: Stephen Rothwell > Cc: Alexander Aring

Re: linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, On Mon, 14 Sep 2015 10:22:34 +1000 Stephen Rothwell wrote: > > On Mon, 14 Sep 2015 10:14:28 +1000 Stephen Rothwell > wrote: > > > > I applied the patches that Andrew has had in his post merge series > > (but I think you were sent a

Re: linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, On Mon, 14 Sep 2015 10:14:28 +1000 Stephen Rothwell wrote: > > I applied the patches that Andrew has had in his post merge series > (but I think you were sent a rolled up version): Actually it was sent by Alexander to Marcel: From: Alexander Aring To: mar...@holtmann.org Cc:

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/ieee802154/at86rf230.c: In function 'at86rf230_s tats_show': drivers/net/ieee802154/at86rf230.c:1650:6: error: void value not ignored as it ought to be ret =

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/ieee802154/at86rf230.c: In function 'at86rf230_s tats_show': drivers/net/ieee802154/at86rf230.c:1650:6: error: void value not ignored as it ought to be ret =

Re: linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, On Mon, 14 Sep 2015 10:14:28 +1000 Stephen Rothwell wrote: > > I applied the patches that Andrew has had in his post merge series > (but I think you were sent a rolled up version): Actually it was sent by Alexander to Marcel: From: Alexander Aring

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/bluetooth/hci_bcm.c: In function 'bcm_acpi_probe': drivers/bluetooth/hci_bcm.c:458:2: error: implicit declaration of function 'acpi_dev_get_resources'

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/bluetooth/hci_bcm.c: In function 'bcm_acpi_probe': drivers/bluetooth/hci_bcm.c:458:2: error: implicit declaration of function 'acpi_dev_get_resources'

Re: linux-next: build failure after merge of the bluetooth tree

Hi Stephen, On Mon, Oct 27, 2014, Stephen Rothwell wrote: > After merging the bluetooth tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > net/bluetooth/smp.o: In function `test_smp': > smp.c:(.init.text+0x0): multiple definition of `init_module' >

Re: linux-next: build failure after merge of the bluetooth tree

Hi Stephen, On Mon, Oct 27, 2014, Stephen Rothwell wrote: After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: net/bluetooth/smp.o: In function `test_smp': smp.c:(.init.text+0x0): multiple definition of `init_module'

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: net/bluetooth/smp.o: In function `test_smp': smp.c:(.init.text+0x0): multiple definition of `init_module' net/bluetooth/af_bluetooth.o:af_bluetooth.c:(.init.text+0x0): first defined

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: net/bluetooth/smp.o: In function `test_smp': smp.c:(.init.text+0x0): multiple definition of `init_module' net/bluetooth/af_bluetooth.o:af_bluetooth.c:(.init.text+0x0): first defined

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/bluetooth/btusb.c:100:2: error: expected '}' before '{' token Caused by commit 493969cf4728 ("Bluetooth: Add support for BCM20702A0 [04ca, 2003]"). That wasn't really well

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/bluetooth/btusb.c:100:2: error: expected '}' before '{' token Caused by commit 493969cf4728 (Bluetooth: Add support for BCM20702A0 [04ca, 2003]). That wasn't really well