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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2198253.9o76ZdvQCi@n9w6sw14>
Date: Tue, 15 Jul 2025 06:36:09 +0200
From: Christian Eggers <ceggers@...i.de>
To: Marcel Holtmann <marcel@...tmann.org>, Johan Hedberg
	<johan.hedberg@...il.com>, Stephen Rothwell <sfr@...b.auug.org.au>
CC: Luiz Augusto von Dentz <luiz.von.dentz@...el.com>, Linux Kernel Mailing
 List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
	<linux-next@...r.kernel.org>, Kiran K <kiran.k@...el.com>, Ivan Pravdin
	<ipravdin.official@...il.com>
Subject: Re: linux-next: build failure after merge of the bluetooth tree

On Tuesday, 15 July 2025, 05:09:32 CEST, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the bluetooth tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/bluetooth/hci_ll.c: In function 'll_setup':
> drivers/bluetooth/hci_ll.c:652:60: error: 'struct hci_dev' has no member named 'quirks'
>   652 |                 set_bit(HCI_QUIRK_INVALID_BDADDR, &hu->hdev->quirks);
>       |                                                            ^~
> drivers/bluetooth/hci_ll.c:656:68: error: 'struct hci_dev' has no member named 'quirks'
>   656 |                         set_bit(HCI_QUIRK_INVALID_BDADDR, &hu->hdev->quirks);
>       |                                                                    ^~
> 
> Caused by commit
> 
>   be736f5f89d5 ("Bluetooth: hci_dev: replace 'quirks' integer by 'quirk_flags' bitmap")
> 
> I have used te bluetooth tree from next-20250714 fo today.
> 
> 

Sorry for this, it was already too late yesterday...

Kiran K. already wrote a fix for this:

https://lore.kernel.org/linux-bluetooth/20250715030318.1007009-1-kiran.k@intel.com/

I hope that's all what I missed.

regards,
Christian