From: Javier Tia <floss@jetm.me>
To: Paul Menzel <pmenzel@molgen.mpg.de>
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>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Jose Tiburcio Ribeiro Netto <jnetto@mineiro.io>,
Ivan Lubnin <lubnin.ivan@gmail.com>
Subject: Re: [PATCH v5 8/8] Bluetooth: btusb: Add MT7927 ID for ASUS X870E / ProArt X870E-Creator
Date: Tue, 31 Mar 2026 14:58:59 -0600 [thread overview]
Message-ID: <20260331210402.DCE821EA006B@mailuser.phl.internal> (raw)
In-Reply-To: 11effdbc-4eff-4430-a22f-3320f84859fb@molgen.mpg.de
Hi Paul,
Thank you for the review.
On Mon, 31 Mar 2026 Paul Menzel wrote:
> > + { USB_DEVICE(0x13d3, 0x3588), .driver_info = BTUSB_MEDIATEK |
> > + BTUSB_WIDEBAND_SPEECH },
>
> This is not sorted. Is there a reason to place it here?
The placement is a consequence of the series structure - each USB ID
patch inserts after the previous one to keep patches independent and
conflict-free. The existing 0x13d3 MediaTek entries in the table are
also not strictly sorted (e.g. 3560, 3620, 3621, 3622, 3563, 3564),
as they are grouped by chip generation rather than numerical order.
That said, Luiz has already applied v4 of this series to
bluetooth-next with this ordering, so any resorting would need a
separate follow-up patch.
Best,
Javier
next reply other threads:[~2026-03-31 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 20:58 Javier Tia [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-31 17:09 [PATCH v5 0/8] Bluetooth: Add MediaTek MT7927 (MT6639) support Javier Tia
2026-03-31 17:09 ` [PATCH v5 8/8] Bluetooth: btusb: Add MT7927 ID for ASUS X870E / ProArt X870E-Creator Javier Tia
2026-03-31 18:13 ` Paul Menzel
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=20260331210402.DCE821EA006B@mailuser.phl.internal \
--to=floss@jetm.me \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jnetto@mineiro.io \
--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=lubnin.ivan@gmail.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=pmenzel@molgen.mpg.de \
/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