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-08-31
Date: Mon, 31 Aug 2026 14:18:37 -0400 [thread overview]
Message-ID: <20260831181837.946230-1-luiz.dentz@gmail.com> (raw)
The following changes since commit 1376afc7660bad2a1a5ee0876898312a486cf8bd:
octeontx2-af: fix CN20K default MCAM rule removal on port cleanup (2026-08-31 10:04:32 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2026-08-31
for you to fetch changes up to 2deb76c21b81e42b3282224f7dd2046fe73fd1e0:
Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (2026-08-31 14:05:27 -0400)
----------------------------------------------------------------
bluetooth pull request for net:
Core:
- hci_core: Fix race condition during device registration
- L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan
- L2CAP: fix out-of-bounds write in l2cap_ecred_connect
- L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM
Drivers:
- hci_mrvl: Fix wrong return value check of wait_on_bit_timeout()
- btintel_pcie: Clear automask on spurious interrupts
- btintel: validate version TLV value lengths
- btintel: bound firmware ID by TLV length
- btintel: propagate version TLV parsing errors
----------------------------------------------------------------
Aleksandr Nogikh (1):
Bluetooth: hci_core: Fix race condition during device registration
Gongwei Li (1):
Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout()
Kiran K (1):
Bluetooth: btintel_pcie: Clear automask on spurious interrupts
Laxman Acharya Padhya (3):
Bluetooth: btintel: validate version TLV value lengths
Bluetooth: btintel: bound firmware ID by TLV length
Bluetooth: btintel: propagate version TLV parsing errors
Pauli Virtanen (3):
Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan
Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect
Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM
drivers/bluetooth/btintel.c | 44 ++++++++++++++++++++++++++++++++++++----
drivers/bluetooth/btintel_pcie.c | 3 +++
drivers/bluetooth/hci_mrvl.c | 3 +--
net/bluetooth/hci_core.c | 4 ++--
net/bluetooth/l2cap_core.c | 33 +++++++++++++++++++++++-------
net/bluetooth/msft.c | 2 +-
6 files changed, 73 insertions(+), 16 deletions(-)
next reply other threads:[~2026-08-31 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 18:18 Luiz Augusto von Dentz [this message]
2026-09-01 0:20 ` [GIT PULL] bluetooth 2026-08-31 patchwork-bot+netdevbpf
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=20260831181837.946230-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 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.