From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: davem@davemloft.net, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [GIT PULL] bluetooth-next 2026-04-10
Date: Sun, 12 Apr 2026 09:16:14 -0700 [thread overview]
Message-ID: <20260412091614.1786af4e@kernel.org> (raw)
In-Reply-To: <20260410172206.150975-1-luiz.dentz@gmail.com>
On Fri, 10 Apr 2026 13:22:06 -0400 Luiz Augusto von Dentz wrote:
> bluetooth-next pull request for net-next:
>
> core:
> - hci_core: Rate limit the logging of invalid ISO handle
> - hci_sync: make hci_cmd_sync_run_once return -EEXIST if exists
> - hci_event: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER
> - hci_event: fix potential UAF in SSP passkey handlers
> - HCI: Avoid a couple -Wflex-array-member-not-at-end warnings
> - L2CAP: CoC: Disconnect if received packet size exceeds MPS
> - L2CAP: Add missing chan lock in l2cap_ecred_reconf_rsp
> - L2CAP: Fix printing wrong information if SDU length exceeds MTU
> - SCO: check for codecs->num_codecs == 1 before assigning to sco_pi(sk)->codec
>
> drivers:
> - btusb: MT7922: Add VID/PID 0489/e174
> - btusb: Add Lite-On 04ca:3807 for MediaTek MT7921
> - btusb: Add MT7927 IDs ASUS ROG Crosshair X870E Hero, Lenovo Legion Pro 7
> 16ARX9, Gigabyte Z790 AORUS MASTER X, MSI X870E Ace Max, TP-Link
> Archer TBE550E, ASUS X870E / ProArt X870E-Creator.
> - btusb: Add MT7902 IDs 13d3/3579, 13d3/3580, 13d3/3594, 13d3/3596, 0e8d/1ede
> - btusb: MediaTek MT7922: Add VID 0489 & PID e11d
> - btintel: Add support for Scorpious Peak2 support
> - btintel: Add support for Scorpious Peak2F support
> - btintel_pcie: Add device id of Scorpius Peak2, Nova Lake-PCD-H
> - btintel_pcie: Add device id of Scorpious2, Nova Lake-PCD-S
> - btmtk: Add reset mechanism if downloading firmware failed
> - btmtk: Add MT6639 (MT7927) Bluetooth support
> - btmtk: fix ISO interface setup for single alt setting
> - btmtk: add MT7902 SDIO support
> - Bluetooth: btmtk: add MT7902 MCU support
> - btbcm: Add entry for BCM4343A2 UART Bluetooth
> - qca: enable pwrseq support for wcn39xx devices
> - hci_qca: Fix BT not getting powered-off on rmmod
> - hci_qca: disable power control for WCN7850 when bt_en is not defined
> - hci_qca: Fix missing wakeup during SSR memdump handling
> - hci_ldisc: Clear HCI_UART_PROTO_INIT on error
> - mmc: sdio: add MediaTek MT7902 SDIO device ID
> - hci_ll: Enable BROKEN_ENHANCED_SETUP_SYNC_CONN for WL183x
Two fixes tags are messed up here:
Commit: 802446198014 ("Bluetooth: btmtk: hide unused btmtk_mt6639_devs[] array")
Fixes tag: Fixes: 4cdd001ff03f ("Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support")
Has these problem(s):
- Target SHA1 does not exist
Commit: 28c9cc700e30 ("Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU")
Fixes tag: Fixes: fa768fce4aae ("Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU")
Has these problem(s):
- Target SHA1 does not exist
next prev parent reply other threads:[~2026-04-12 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 17:22 [GIT PULL] bluetooth-next 2026-04-10 Luiz Augusto von Dentz
2026-04-12 16:16 ` Jakub Kicinski [this message]
2026-04-13 20:07 ` Luiz Augusto von Dentz
2026-04-13 20:44 ` Jakub Kicinski
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=20260412091614.1786af4e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@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.