From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Alexander Tsoy <alexander@tsoy.me>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y 5/6] Bluetooth: btusb: Add new VID/PID for WCN785x
Date: Thu, 1 May 2025 14:51:35 -0400 [thread overview]
Message-ID: <20250501121434-b84a545ea5d6c24c@stable.kernel.org> (raw)
In-Reply-To: <20250430230616.4023290-6-alexander@tsoy.me>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: c7629ccfa175e16bb44a60c469214e1a6051f63d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Alexander Tsoy<alexander@tsoy.me>
Commit author: Dorian Cruveiller<doriancruveiller@gmail.com>
Status in newer kernel trees:
6.14.y | Present (different SHA1: 8f67322e6990)
Note: The patch differs from the upstream commit:
---
1: c7629ccfa175e ! 1: 5622b0e1b9ca6 Bluetooth: btusb: Add new VID/PID for WCN785x
@@ Metadata
## Commit message ##
Bluetooth: btusb: Add new VID/PID for WCN785x
+ [ Upstream commit c7629ccfa175e16bb44a60c469214e1a6051f63d ]
+
Add VID 0489 & PID e10d for Qualcomm WCN785x USB Bluetooth chip.
The information in /sys/kernel/debug/usb/devices about the Bluetooth
@@ Commit message
Signed-off-by: Dorian Cruveiller <doriancruveiller@gmail.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
+ Signed-off-by: Alexander Tsoy <alexander@tsoy.me>
## drivers/bluetooth/btusb.c ##
@@ drivers/bluetooth/btusb.c: static const struct usb_device_id quirks_table[] = {
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
next prev parent reply other threads:[~2025-05-01 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 23:05 [PATCH 6.12.y 0/6] Bluetooth: btusb: add a bunch of USB device IDs for Qualcomm WCN785x Alexander Tsoy
2025-04-30 23:05 ` [PATCH 6.12.y 1/6] Bluetooth: btusb: add Foxconn 0xe0fc " Alexander Tsoy
2025-05-01 18:51 ` Sasha Levin
2025-04-30 23:05 ` [PATCH 6.12.y 2/6] Bluetooth: btusb: Add one more ID 0x0489:0xe0f3 " Alexander Tsoy
2025-05-01 19:09 ` Sasha Levin
2025-04-30 23:05 ` [PATCH 6.12.y 3/6] Bluetooth: btusb: Add one more ID 0x13d3:0x3623 " Alexander Tsoy
2025-05-01 18:51 ` Sasha Levin
2025-04-30 23:05 ` [PATCH 6.12.y 4/6] Bluetooth: btusb: Add ID 0x2c7c:0x0130 " Alexander Tsoy
2025-05-01 19:11 ` Sasha Levin
2025-04-30 23:05 ` [PATCH 6.12.y 5/6] Bluetooth: btusb: Add new VID/PID for WCN785x Alexander Tsoy
2025-05-01 18:51 ` Sasha Levin [this message]
2025-04-30 23:05 ` [PATCH 6.12.y 6/6] Bluetooth: btusb: Add 13 USB device IDs for Qualcomm WCN785x Alexander Tsoy
2025-05-01 18:51 ` Sasha Levin
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=20250501121434-b84a545ea5d6c24c@stable.kernel.org \
--to=sashal@kernel.org \
--cc=alexander@tsoy.me \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.