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-10-05
Date: Mon, 5 Oct 2026 15:44:36 -0400 [thread overview]
Message-ID: <20261005194436.3594085-1-luiz.dentz@gmail.com> (raw)
The following changes since commit 848a7a91c7f03675d3bd8db6f7721cbf9cb50e21:
Bluetooth: hci_core: Serialize SCO and ISO scheduling with teardown (2026-09-28 11:00:20 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2026-10-05
for you to fetch changes up to e32d80293a0e1a160d5e5101daa8c82148c07510:
Bluetooth: ISO: Serialize concurrent connect calls (2026-10-05 13:10:47 -0400)
----------------------------------------------------------------
bluetooth pull request for net:
Core:
- hci_sync: Fix command skb lifetime during scan setup
- hci_sock: Serialize dead-device detachment
- RFCOMM: free the skb when the DLC has no owner
- RFCOMM: connect the session socket without rfcomm_mutex
- RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown
- SCO: serialise sco_conn lifetime against sco_recv_scodata()
- ISO: Reject concurrent BIS listener setup
- ISO: Serialize concurrent connect calls
- MGMT: Fix status of pending commands flushed on power off
Driver:
- btintel_pcie: fix TX descriptor bounds check
- btintel_pcie: use managed IRQ teardown
- btintel_pcie: Add shared HW reset for clean start
----------------------------------------------------------------
Aldo Ariel Panzardo (1):
Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata()
Chengfeng Ye (4):
Bluetooth: hci_sock: Serialize dead-device detachment
Bluetooth: hci_sync: Fix command skb lifetime during scan setup
Bluetooth: ISO: Reject concurrent BIS listener setup
Bluetooth: ISO: Serialize concurrent connect calls
Iaroslav Voitovych (1):
Bluetooth: MGMT: Fix status of pending commands flushed on power off
Maxim Skokov (1):
Bluetooth: RFCOMM: free the skb when the DLC has no owner
Mikhail Gavrilov (1):
Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex
Palla Raghunath (1):
Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown
Ravindra (1):
Bluetooth: btintel_pcie: fix TX descriptor bounds check
Runyu Xiao (1):
Bluetooth: btintel_pcie: use managed IRQ teardown
Sai Teja Aluvala (1):
Bluetooth: btintel_pcie: Add shared HW reset for clean start
drivers/bluetooth/btintel_pcie.c | 17 ++++-
include/net/bluetooth/rfcomm.h | 1 +
net/bluetooth/hci_core.c | 4 ++
net/bluetooth/hci_sock.c | 2 +
net/bluetooth/hci_sync.c | 10 ++-
net/bluetooth/iso.c | 52 ++++++++++++---
net/bluetooth/mgmt.c | 2 +-
net/bluetooth/rfcomm/core.c | 134 +++++++++++++++++++++++++++------------
net/bluetooth/rfcomm/sock.c | 5 +-
net/bluetooth/rfcomm/tty.c | 2 +-
net/bluetooth/sco.c | 87 ++++++++++++++++++-------
11 files changed, 238 insertions(+), 78 deletions(-)
next reply other threads:[~2026-10-05 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 19:44 Luiz Augusto von Dentz [this message]
2026-10-07 0:50 ` [GIT PULL] bluetooth 2026-10-05 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=20261005194436.3594085-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