From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Marcel Holtmann <marcel@holtmann•org>,
Johan Hedberg <johan.hedberg@gmail•com>,
David Miller <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>
Cc: Networking <netdev@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the bluetooth tree
Date: Mon, 18 Aug 2025 10:51:15 +1000 [thread overview]
Message-ID: <20250818105115.2adf8ef8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2464 bytes --]
Hi all,
The following commits are also in the net tree as different commits
(but the same patches):
3ae443de7edf ("Bluetooth: hci_core: Fix not accounting for BIS/CIS/PA links separately")
3f9a516852b6 ("Bluetooth: btnxpuart: Uses threaded IRQ for host wakeup handling")
8477821d5f12 ("Bluetooth: hci_conn: do return error from hci_enhanced_setup_sync()")
ad2f0c8792ef ("Bluetooth: hci_event: fix MTU for BN == 0 in CIS Established")
3e383124ce63 ("Bluetooth: hci_sync: Prevent unintended PA sync when SID is 0xFF")
c244fc08ac4e ("Bluetooth: hci_core: Fix using ll_privacy_capable for current settings")
3ca23aaba210 ("Bluetooth: hci_core: Fix using {cis,bis}_capable for current settings")
5ecd1fbdacce ("Bluetooth: btmtk: Fix wait_on_bit_timeout interruption during shutdown")
9c533991fe15 ("Bluetooth: hci_conn: Fix not cleaning up Broadcaster/Broadcast Source")
b69b1f91b84d ("Bluetooth: hci_conn: Fix running bis_cleanup for hci_conn->type PA_LINK")
408410a0a0cb ("Bluetooth: ISO: Fix getname not returning broadcast fields")
dc996aa11328 ("Bluetooth: hci_sync: Fix scan state after PA Sync has been established")
fdbb50f1b26d ("Bluetooth: hci_sync: Avoid adding default advertising on startup")
These are commits
9d4b01a0bf8d ("Bluetooth: hci_core: Fix not accounting for BIS/CIS/PA links separately")
e489317d2fd9 ("Bluetooth: btnxpuart: Uses threaded IRQ for host wakeup handling")
0eaf7c7e85da ("Bluetooth: hci_conn: do return error from hci_enhanced_setup_sync()")
0b3725dbf61b ("Bluetooth: hci_event: fix MTU for BN == 0 in CIS Established")
4d19cd228bbe ("Bluetooth: hci_sync: Prevent unintended PA sync when SID is 0xFF")
3dcf7175f2c0 ("Bluetooth: hci_core: Fix using ll_privacy_capable for current settings")
709788b154ca ("Bluetooth: hci_core: Fix using {cis,bis}_capable for current settings")
099799fa9b76 ("Bluetooth: btmtk: Fix wait_on_bit_timeout interruption during shutdown")
3ba486c5f3ce ("Bluetooth: hci_conn: Fix not cleaning up Broadcaster/Broadcast Source")
d36349ea73d8 ("Bluetooth: hci_conn: Fix running bis_cleanup for hci_conn->type PA_LINK")
aee29c18a38d ("Bluetooth: ISO: Fix getname not returning broadcast fields")
ca88be1a2725 ("Bluetooth: hci_sync: Fix scan state after PA Sync has been established")
de5d7d3f27dd ("Bluetooth: hci_sync: Avoid adding default advertising on startup")
in the net tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-08-18 0:51 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 0:51 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-04 21:48 linux-next: duplicate patches in the bluetooth tree Stephen Rothwell
2025-11-12 23:44 Stephen Rothwell
2025-10-28 23:31 Stephen Rothwell
2025-09-02 1:23 Stephen Rothwell
2025-08-25 1:06 Stephen Rothwell
2025-07-02 2:12 Stephen Rothwell
2025-06-25 1:16 Stephen Rothwell
2025-06-25 7:24 ` Paolo Abeni
2025-06-12 22:10 Stephen Rothwell
2025-06-10 2:26 Stephen Rothwell
2025-06-03 4:02 Stephen Rothwell
2025-05-21 3:53 Stephen Rothwell
2025-04-30 2:44 Stephen Rothwell
2025-04-14 3:07 Stephen Rothwell
2025-03-20 1:12 Stephen Rothwell
2025-03-11 2:04 Stephen Rothwell
2025-03-03 1:25 Stephen Rothwell
2025-02-27 20:42 Stephen Rothwell
2025-02-24 2:17 Stephen Rothwell
2025-02-13 21:19 Stephen Rothwell
2025-01-31 2:16 Stephen Rothwell
2025-01-31 7:37 ` Paolo Abeni
2025-01-10 0:44 Stephen Rothwell
2024-12-08 20:39 Stephen Rothwell
2024-11-14 0:54 Stephen Rothwell
2024-10-25 2:09 Stephen Rothwell
2024-10-21 6:43 Stephen Rothwell
2024-10-09 0:49 Stephen Rothwell
2024-10-03 22:42 Stephen Rothwell
2024-09-04 2:28 Stephen Rothwell
2024-08-27 1:27 Stephen Rothwell
2024-08-19 1:01 Stephen Rothwell
2024-08-23 3:56 ` Stephen Rothwell
2024-08-08 22:49 Stephen Rothwell
2024-07-28 23:56 Stephen Rothwell
2024-07-02 1:47 Stephen Rothwell
2024-06-13 0:53 Stephen Rothwell
2024-04-25 21:09 Stephen Rothwell
2024-05-06 1:33 ` Stephen Rothwell
2024-04-11 21:34 Stephen Rothwell
2024-04-01 23:37 Stephen Rothwell
2024-02-29 22:25 Stephen Rothwell
2023-12-21 1:24 Stephen Rothwell
2023-12-21 21:41 ` Stephen Rothwell
2023-10-18 3:14 Stephen Rothwell
2023-10-19 21:23 ` Stephen Rothwell
2023-10-05 22:02 Stephen Rothwell
2023-10-03 1:19 Stephen Rothwell
2023-07-23 22:44 Stephen Rothwell
2023-07-06 2:35 Stephen Rothwell
2023-06-30 0:21 Stephen Rothwell
2023-06-08 0:47 Stephen Rothwell
2023-05-29 21:59 Stephen Rothwell
2023-03-24 1:21 Stephen Rothwell
2023-03-26 20:47 ` Stephen Rothwell
2023-01-19 0:48 Stephen Rothwell
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=20250818105115.2adf8ef8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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