From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: linux-next: duplicate patches in the bluetooth tree
Date: Mon, 27 Mar 2023 07:47:34 +1100 [thread overview]
Message-ID: <20230327074734.4bd3af8e@canb.auug.org.au> (raw)
In-Reply-To: <20230324122159.0f34ffcb@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
Hi all,
On Fri, 24 Mar 2023 12:21:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The following commits are also in the net tree as different commits
> (but the same patches):
>
> 0b0501e48331 ("Bluetooth: Fix race condition in hci_cmd_sync_clear")
> 1446dcd9dcfc ("Bluetooth: btintel: Iterate only bluetooth device ACPI entries")
> 23942ce75b8c ("Bluetooth: L2CAP: Fix responding with wrong PDU type")
> 363bb3fbb249 ("Bluetooth: hci_core: Detect if an ACL packet is in fact an ISO packet")
> 36ecf4d48b5a ("Bluetooth: btusb: Remove detection of ISO packets over bulk")
> 3ebbba4feafd ("Bluetooth: btqcomsmd: Fix command timeout after setting BD address")
> 592916198977 ("Bluetooth: ISO: fix timestamped HCI ISO data packet parsing")
> 59ba62c59bfe ("Bluetooth: HCI: Fix global-out-of-bounds")
> 6eaae76b4aed ("Bluetooth: btsdio: fix use after free bug in btsdio_remove due to unfinished work")
> 81183a159b36 ("Bluetooth: hci_sync: Resume adv with no RPA when active scan")
> 853c3e629079 ("Bluetooth: mgmt: Fix MGMT add advmon with RSSI command")
> 906d721e4897 ("Bluetooth: btinel: Check ACPI handle for NULL before accessing")
> bfcd8f0d273d ("Bluetooth: Remove "Power-on" check from Mesh feature")
These commits are now in Linus' tree as different commits but the same patches.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-26 20:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 1:21 linux-next: duplicate patches in the bluetooth tree Stephen Rothwell
2023-03-26 20:47 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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=20230327074734.4bd3af8e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).