From: Paolo Abeni <pabeni@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Marcel Holtmann <marcel@holtmann•org>,
Johan Hedberg <johan.hedberg@gmail•com>,
David Miller <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
Luiz Augusto von Dentz <luiz.dentz@gmail•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: Re: linux-next: duplicate patches in the bluetooth tree
Date: Wed, 25 Jun 2025 09:24:52 +0200 [thread overview]
Message-ID: <81a216e8-e675-4564-84bb-039e0851a8ec@redhat.com> (raw)
In-Reply-To: <20250625111648.54026af1@canb.auug.org.au>
Hi,
On 6/25/25 3:16 AM, Stephen Rothwell wrote:
> 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.
I think it's an artifact of the BT tree being rebased. I pulled from:
git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git
tags/for-net-2025-06-23
It looks like the first set of commits is no more reachable in the bt
tree, so the 'net' ones should be the "correct" commits set. @Luiz:
could you please confirm?
Thanks,
Paolo
next prev parent reply other threads:[~2025-06-25 7:25 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 1:16 linux-next: duplicate patches in the bluetooth tree Stephen Rothwell
2025-06-25 7:24 ` Paolo Abeni [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-04 21:48 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-08-18 0:51 Stephen Rothwell
2025-07-02 2:12 Stephen Rothwell
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=81a216e8-e675-4564-84bb-039e0851a8ec@redhat.com \
--to=pabeni@redhat$(echo .)com \
--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=luiz.dentz@gmail$(echo .)com \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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