[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250625111648.54026af1@canb.auug.org.au>
Date: Wed, 25 Jun 2025 11:16:48 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Marcel Holtmann <marcel@...tmann.org>, Johan Hedberg
<johan.hedberg@...il.com>, David Miller <davem@...emloft.net>, Jakub
Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Cc: Networking <netdev@...r.kernel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>
Subject: linux-next: duplicate patches in the bluetooth tree
Hi all,
The following commits are also in the net tree as different commits
(but the same patches):
4500d2e8da07 ("Bluetooth: hci_core: Fix use-after-free in vhci_flush()")
6c31dab4ff1e ("driver: bluetooth: hci_qca:fix unable to load the BT driver")
d5c2d5e0f1d3 ("Bluetooth: L2CAP: Fix L2CAP MTU negotiation")
866fd57640ce ("Bluetooth: btintel_pcie: Fix potential race condition in firmware download")
These are commits
1d6123102e9f ("Bluetooth: hci_core: Fix use-after-free in vhci_flush()")
db0ff7e15923 ("driver: bluetooth: hci_qca:fix unable to load the BT driver")
042bb9603c44 ("Bluetooth: L2CAP: Fix L2CAP MTU negotiation")
89a33de31494 ("Bluetooth: btintel_pcie: Fix potential race condition in firmware download")
in the net tree.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists