From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Cc: Kiran K <kiran.k@intel.com>,
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>
Subject: linux-next: build warning after merge of the bluetooth tree
Date: Wed, 8 May 2024 12:24:32 +1000 [thread overview]
Message-ID: <20240508122432.6579321b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
Hi all,
After merging the bluetooth tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from drivers/bluetooth/hci_ldisc.c:34:
drivers/bluetooth/btintel.h:373:13: warning: 'btintel_hw_error' defined but not used [-Wunused-function]
373 | static void btintel_hw_error(struct hci_dev *hdev, u8 code)
| ^~~~~~~~~~~~~~~~
Introduced by commit
1d8e17157eb5 ("Bluetooth: btintel: Export few static functions")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-08 2:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 2:24 Stephen Rothwell [this message]
[not found] <PH0PR11MB51264FB7874380983C3A653BD3CF9@PH0PR11MB5126.namprd11.prod.outlook.com>
2022-05-16 18:18 ` linux-next: build warning after merge of the bluetooth tree Yury Norov
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 7:57 Stephen Rothwell
2022-05-23 22:22 ` Stephen Rothwell
2022-06-05 22:06 ` Stephen Rothwell
2022-06-05 22:40 ` Yury Norov
2022-06-06 1:16 ` Stephen Rothwell
2019-11-22 0:07 Stephen Rothwell
2019-03-17 23:30 Stephen Rothwell
2017-11-14 0:56 Stephen Rothwell
2017-11-14 9:00 ` Hans de Goede
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=20240508122432.6579321b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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 \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).