From: Christian Eggers <ceggers@arri.de>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Kiran K <kiran.k@intel.com>,
Ivan Pravdin <ipravdin.official@gmail.com>
Subject: Re: linux-next: build failure after merge of the bluetooth tree
Date: Tue, 15 Jul 2025 06:36:09 +0200 [thread overview]
Message-ID: <2198253.9o76ZdvQCi@n9w6sw14> (raw)
In-Reply-To: <20250715130932.5e13bfb3@canb.auug.org.au>
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
next prev parent reply other threads:[~2025-07-15 4:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 3:09 linux-next: build failure after merge of the bluetooth tree Stephen Rothwell
2025-07-15 4:36 ` Christian Eggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 10:59 Stephen Rothwell
2025-01-10 0:57 Stephen Rothwell
2024-08-30 1:42 Stephen Rothwell
2024-05-01 1:19 Stephen Rothwell
2024-05-01 1:34 ` Sungwoo Kim
2023-07-20 22:21 Iwashima, Kuniyuki
[not found] <PH0PR11MB51269B6805230AB8ED209B14D332A@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-07-20 0:50 ` Stephen Rothwell
2023-07-20 1:24 ` Jakub Kicinski
2023-07-20 3:00 ` Stephen Rothwell
[not found] ` <PH0PR11MB5126763E5913574B8ED6BDE4D33EA@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-07-20 3:24 ` Jakub Kicinski
2023-07-20 6:00 ` Alexander Mikhalitsyn
2023-07-20 15:14 ` Jakub Kicinski
2023-07-20 15:21 ` Alexander Mikhalitsyn
2023-07-20 22:19 ` Stephen Rothwell
2023-07-20 22:12 ` Stephen Rothwell
2023-07-20 23:27 ` Jakub Kicinski
2023-07-20 23:30 ` Stephen Rothwell
[not found] <PH0PR11MB51262F07CD4739BDCB920483D322A@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-06-23 8:34 ` Alexander Mikhalitsyn
2023-06-23 9:23 ` Alexander Mikhalitsyn
2023-06-23 12:24 ` Christian Brauner
2023-06-23 12:28 ` Alexander Mikhalitsyn
2023-06-23 15:09 ` Jakub Kicinski
2023-06-26 22:09 ` Alexander Mikhalitsyn
[not found] <PH0PR11MB5126F2B2E020774AF8D91299D35BA@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-06-15 23:27 ` Stephen Rothwell
2023-06-13 3:02 Stephen Rothwell
2023-06-15 22:32 ` Stephen Rothwell
2023-07-06 23:41 ` Stephen Rothwell
2021-12-07 0:26 Stephen Rothwell
2021-12-06 0:37 Stephen Rothwell
2021-09-27 0:16 Stephen Rothwell
[not found] <PH0PR11MB5126EFEDB65650EFC3368981D3749@PH0PR11MB5126.namprd11.prod.outlook.com>
2021-04-08 4:57 ` Stephen Rothwell
2021-04-08 3:59 Stephen Rothwell
2020-07-27 3:44 Stephen Rothwell
2020-07-27 5:22 ` Christoph Hellwig
2020-07-27 13:28 ` Alain Michaud
2019-10-18 0:13 Stephen Rothwell
2015-09-14 0:14 Stephen Rothwell
2015-09-14 0:22 ` Stephen Rothwell
2015-09-22 1:20 ` Stephen Rothwell
2015-09-22 3:42 ` David Miller
2015-08-12 8:01 Stephen Rothwell
2014-10-27 2:19 Stephen Rothwell
2014-10-28 14:49 ` Johan Hedberg
2012-09-19 1:45 Stephen Rothwell
2012-02-22 1:21 Stephen Rothwell
2012-02-22 1:29 ` David Miller
2011-12-21 2:19 Stephen Rothwell
2011-04-28 1:41 Stephen Rothwell
2011-04-28 4:12 ` Gustavo F. Padovan
2011-02-15 2:16 Stephen Rothwell
2011-02-15 12:48 ` Gustavo F. Padovan
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=2198253.9o76ZdvQCi@n9w6sw14 \
--to=ceggers@arri.de \
--cc=ipravdin.official@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=kiran.k@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=sfr@canb.auug.org.au \
/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