From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: [GIT PULL] bluetooth 2026-02-23
Date: Mon, 23 Feb 2026 16:16:34 -0500 [thread overview]
Message-ID: <20260223211634.3800315-1-luiz.dentz@gmail.com> (raw)
The following changes since commit d4f687fbbce45b5e88438e89b5e26c0c15847992:
ovpn: tcp - fix packet extraction from stream (2026-02-21 07:04:08 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2026-02-23
for you to fetch changes up to 138d7eca445ef37a0333425d269ee59900ca1104:
Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ (2026-02-23 16:08:15 -0500)
----------------------------------------------------------------
bluetooth pull request for net:
- purge error queues in socket destructors
- hci_sync: Fix CIS host feature condition
- L2CAP: Fix invalid response to L2CAP_ECRED_RECONF_REQ
- L2CAP: Fix result of L2CAP_ECRED_CONN_RSP when MTU is too short
- L2CAP: Fix response to L2CAP_ECRED_CONN_REQ
- L2CAP: Fix not checking output MTU is acceptable on L2CAP_ECRED_CONN_REQ
- L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ
- hci_qca: Cleanup on all setup failures
----------------------------------------------------------------
Heitor Alves de Siqueira (1):
Bluetooth: purge error queues in socket destructors
Jinwang Li (1):
Bluetooth: hci_qca: Cleanup on all setup failures
Luiz Augusto von Dentz (5):
Bluetooth: L2CAP: Fix invalid response to L2CAP_ECRED_RECONF_REQ
Bluetooth: L2CAP: Fix result of L2CAP_ECRED_CONN_RSP when MTU is too short
Bluetooth: L2CAP: Fix response to L2CAP_ECRED_CONN_REQ
Bluetooth: L2CAP: Fix not checking output MTU is acceptable on L2CAP_ECRED_CONN_REQ
Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ
Mariusz Skamra (1):
Bluetooth: Fix CIS host feature condition
drivers/bluetooth/hci_qca.c | 24 ++++++-----
include/net/bluetooth/l2cap.h | 8 ++--
net/bluetooth/hci_sock.c | 1 +
net/bluetooth/hci_sync.c | 2 +-
net/bluetooth/iso.c | 1 +
net/bluetooth/l2cap_core.c | 95 +++++++++++++++++++++++++++++++------------
net/bluetooth/l2cap_sock.c | 16 ++++++--
net/bluetooth/sco.c | 1 +
8 files changed, 105 insertions(+), 43 deletions(-)
next reply other threads:[~2026-02-23 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 21:16 Luiz Augusto von Dentz [this message]
2026-02-25 0:29 ` [GIT PULL] bluetooth 2026-02-23 Jakub Kicinski
2026-03-16 19:42 ` patchwork-bot+bluetooth
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=20260223211634.3800315-1-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox