Linux bluetooth development
 help / color / mirror / Atom feed
From: Kenzi Voyer <kenzivoyer@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Add USB ID 13d3:3631 for MediaTek MT7925
Date: Thu, 24 Sep 2026 18:01:24 +0200	[thread overview]
Message-ID: <20260924160128.2128261-1-kenzivoyer@gmail.com> (raw)
In-Reply-To: <20260924115328.15987-1-kenzivoyer@gmail.com>

Please disregard this patch.

As the CI bot notes, it no longer applies because drivers/bluetooth/btusb.c
has since been restructured. More importantly, Samuel Alhovuori already
submitted this same addition and his v2 was applied to bluetooth-next on
2026-09-08, so USB ID 13d3:3631 is already present in the current tree
(drivers/bluetooth/btusb_main.c).

Apologies for the duplicate submission and the noise.

Best regards,
Kenzi Voyer

      parent reply	other threads:[~2026-09-24 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 11:53 [PATCH] Bluetooth: btusb: Add USB ID 13d3:3631 for MediaTek MT7925 Kenzi Voyer
2026-09-24 15:01 ` bluez.test.bot
2026-09-24 16:01 ` Kenzi Voyer [this message]

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=20260924160128.2128261-1-kenzivoyer@gmail.com \
    --to=kenzivoyer@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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