public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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: Thu, 05 Mar 2026 16:56:47 -0600	[thread overview]
Message-ID: <20260305225927.671361EA006B@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.

Good idea. I'll split patch 2/2 into per-device commits so each USB
ID has a clear Tested-by trail. The split will be:

  - 0489:e0fa (Lenovo Legion Pro 7)
  - 0489:e10f (Gigabyte Z790/X870E boards)
  - 0489:e116 (TP-Link Archer TBE550E)
  - 0489:e13a (ASUS X870E boards)
  - 13d3:3588 (ASUS ProArt X870E-Creator)

> 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.

Understood. Each commit will include lsusb + dmesg snippets in the
body and a Link: tag pointing to the full hardware report.

I'm collecting the Tested-by consents now. Will send v2 once I have
them all.

Javier

             reply	other threads:[~2026-03-05 22:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 22:56 Javier Tia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-26  0:18 [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=20260305225927.671361EA006B@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