Message ID | 34A24B6870318797+20240929074852.977045-1-wangyuli@uniontech.com (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | [RESEND.,v2] Bluetooth: btusb: Add MT7925 support for ID 0x13d3:0x3608 | expand |
Context | Check | Description |
---|---|---|
tedd_an/pre-ci_am | fail | error: patch failed: drivers/bluetooth/btusb.c:512 error: drivers/bluetooth/btusb.c: patch does not apply hint: Use 'git am --show-current-patch' to see the failed patch |
This is an automated email and please do not reply to this email. Dear Submitter, Thank you for submitting the patches to the linux bluetooth mailing list. While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository. ----- Output ----- error: patch failed: drivers/bluetooth/btusb.c:512 error: drivers/bluetooth/btusb.c: patch does not apply hint: Use 'git am --show-current-patch' to see the failed patch Please resolve the issue and submit the patches again. --- Regards, Linux Bluetooth
Could anyone shed some light on what's going on here? I'm absolutely certain this patch can be merged directly into the bluetooth-next branch of the bluetooth-next repository (git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git). Am I missing something,or is there a problem with the bot? -- WangYuli
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index cd22b34542d5..4adae0be8222 100644 --- a/drivers/bluetooth/btusb.c +++ b/drivers/bluetooth/btusb.c @@ -512,6 +512,11 @@ static const struct usb_device_id blacklist_table[] = { BTUSB_WIDEBAND_SPEECH | BTUSB_VALID_LE_STATES }, + /* MediaTek MT7925 Bluetooth devices */ + { USB_DEVICE(0x13d3, 0x3608), .driver_info = BTUSB_MEDIATEK | + BTUSB_WIDEBAND_SPEECH | + BTUSB_VALID_LE_STATES }, + /* Additional Realtek 8723AE Bluetooth devices */ { USB_DEVICE(0x0930, 0x021d), .driver_info = BTUSB_REALTEK }, { USB_DEVICE(0x13d3, 0x3394), .driver_info = BTUSB_REALTEK },