From: Javier Tia <floss@jetm.me>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)
Date: Wed, 25 Mar 2026 18:18:45 -0600 [thread overview]
Message-ID: <20260326002245.00F941EA006C@mailuser.phl.internal> (raw)
In-Reply-To: CABBYNZ+PTk5+Dq5p+kHQdmqQshsC1kOzuqqmJtZyF5XAJzLzmA@mail.gmail.com
Hi Luiz,
On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> Let's gather their emails and list them as Tested-by, or perhaps
> we it should really be multiple changes to make easier to trace
> back how it was tested.
Done. v2 splits the USB IDs into per-device commits (6 commits),
each with its own Tested-by trailer from the hardware owner.
> Ok, so Id probably require 'Tested-by' to be a human, and in this
> case, I want the lsusb and dmesg | grep bluetooth either directly
> in the commit message or as a Link so it can be verified.
Each USB ID commit in v2 includes the full USB descriptor output
from /sys/kernel/debug/usb/devices. All Tested-by trailers are
from humans who tested on their own hardware.
Tested-by coverage: 5 of 6 USB IDs have trailers. The one
exception is 0489:e110 (MSI X870E Ace Max) where the user
confirmed it works but has not provided a formal trailer yet.
v2 is sent with all requested changes.
Best,
Javier
next reply other threads:[~2026-03-26 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 0:18 Javier Tia [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-05 22:56 [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639) Javier Tia
2026-03-05 17:18 Javier Tia
2026-03-05 22:39 ` Luiz Augusto von Dentz
2026-03-05 16:04 [PATCH 0/2] Bluetooth: Add MediaTek MT7927 (MT6639) support Javier Tia
2026-03-05 16:05 ` [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639) Javier Tia
2026-03-05 17:00 ` Luiz Augusto von Dentz
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=20260326002245.00F941EA006C@mailuser.phl.internal \
--to=floss@jetm.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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