From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Javier Tia <floss@jetm.me>, Arnd Bergmann <arnd@arndb.de>,
Chris Lu <chris.lu@mediatek.com>, Kees Cook <kees@kernel.org>,
Johan Hovold <johan@kernel.org>,
Sean Wang <sean.wang@mediatek.com>,
Jiande Lu <jiande.lu@mediatek.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] Bluetooth: btmtk: hide unused btmtk_mt6639_devs[] array
Date: Thu, 2 Apr 2026 17:41:25 +0200 [thread overview]
Message-ID: <4736768a-e391-4f70-9821-7386efedf3b3@molgen.mpg.de> (raw)
In-Reply-To: <20260402141119.2732591-1-arnd@kernel.org>
Dear Arnd,
Thank you for your patch.
Am 02.04.26 um 16:11 schrieb Arnd Bergmann:
> From: Arnd Bergmann <arnd@arndb.de>
>
> When USB support is disabled, the array is not referenced anywhere,
> causing a warning:
>
> drivers/bluetooth/btmtk.c:35:3: error: 'btmtk_mt6639_devs' defined but not used [-Werror=unused-const-variable=]
> 35 | } btmtk_mt6639_devs[] = {
> | ^~~~~~~~~~~~~~~~~
>
> Move it into the #ifdef block.
>
> Fixes: 4cdd001ff03f ("Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/bluetooth/btmtk.c | 32 ++++++++++++++++----------------
> 1 file changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/bluetooth/btmtk.c b/drivers/bluetooth/btmtk.c
> index 099188bf772e..6fb6ca274808 100644
> --- a/drivers/bluetooth/btmtk.c
> +++ b/drivers/bluetooth/btmtk.c
> @@ -25,22 +25,6 @@
> /* It is for mt79xx iso data transmission setting */
> #define MTK_ISO_THRESHOLD 264
>
> -/* Known MT6639 (MT7927) Bluetooth USB devices.
> - * Used to scope the zero-CHIPID workaround to real MT6639 hardware,
> - * since some boards return 0x0000 from the MMIO chip ID register.
> - */
> -static const struct {
> - u16 vendor;
> - u16 product;
> -} btmtk_mt6639_devs[] = {
> - { 0x0489, 0xe13a }, /* ASUS ROG Crosshair X870E Hero */
> - { 0x0489, 0xe0fa }, /* Lenovo Legion Pro 7 16ARX9 */
> - { 0x0489, 0xe10f }, /* Gigabyte Z790 AORUS MASTER X */
> - { 0x0489, 0xe110 }, /* MSI X870E Ace Max */
> - { 0x0489, 0xe116 }, /* TP-Link Archer TBE550E */
> - { 0x13d3, 0x3588 }, /* ASUS ROG STRIX X870E-E */
> -};
> -
> struct btmtk_patch_header {
> u8 datetime[16];
> u8 platform[4];
> @@ -483,6 +467,22 @@ int btmtk_process_coredump(struct hci_dev *hdev, struct sk_buff *skb)
> EXPORT_SYMBOL_GPL(btmtk_process_coredump);
>
> #if IS_ENABLED(CONFIG_BT_HCIBTUSB_MTK)
> +/* Known MT6639 (MT7927) Bluetooth USB devices.
> + * Used to scope the zero-CHIPID workaround to real MT6639 hardware,
> + * since some boards return 0x0000 from the MMIO chip ID register.
> + */
> +static const struct {
> + u16 vendor;
> + u16 product;
> +} btmtk_mt6639_devs[] = {
> + { 0x0489, 0xe13a }, /* ASUS ROG Crosshair X870E Hero */
> + { 0x0489, 0xe0fa }, /* Lenovo Legion Pro 7 16ARX9 */
> + { 0x0489, 0xe10f }, /* Gigabyte Z790 AORUS MASTER X */
> + { 0x0489, 0xe110 }, /* MSI X870E Ace Max */
> + { 0x0489, 0xe116 }, /* TP-Link Archer TBE550E */
> + { 0x13d3, 0x3588 }, /* ASUS ROG STRIX X870E-E */
> +};
> +
> static void btmtk_usb_wmt_recv(struct urb *urb)
> {
> struct hci_dev *hdev = urb->context;
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
next prev parent reply other threads:[~2026-04-02 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 14:11 Arnd Bergmann
2026-04-02 15:41 ` Paul Menzel [this message]
2026-04-02 17:40 ` patchwork-bot+bluetooth
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=4736768a-e391-4f70-9821-7386efedf3b3@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=chris.lu@mediatek.com \
--cc=floss@jetm.me \
--cc=jiande.lu@mediatek.com \
--cc=johan@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@mediatek.com \
/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
all inboxes | Powered by JetHome®