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>
Subject: Re: linux-next: duplicate patches in the bluetooth tree
Date: Fri, 20 Oct 2023 08:23:21 +1100 [thread overview]
Message-ID: <20231020082321.46af78d6@canb.auug.org.au> (raw)
In-Reply-To: <20231018141446.19fa9b25@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hi all,
On Wed, 18 Oct 2023 14:14:46 +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):
>
> 0ebb3699b15d ("Bluetooth: vhci: Fix race when opening vhci device")
> 19cb846d0b71 ("Bluetooth: hci_event: Fix using memcmp when comparing keys")
> 27eb5c50277f ("Bluetooth: hci_event: Ignore NULL link key")
> 354eeee644a0 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
> 4025ddca4aa6 ("Bluetooth: ISO: Fix invalid context error")
> 47d973dff74e ("Bluetooth: hci_sock: fix slab oob read in create_monitor_event")
> 505fc3b0f198 ("Bluetooth: btrtl: Ignore error return for hci_devcd_register()")
> 58250a6dc86d ("Bluetooth: Reject connection with the device which has same BD_ADDR")
> 81a220a6c891 ("Bluetooth: hci_event: Fix coding style")
> a86e2622de15 ("Bluetooth: avoid memcmp() out of bounds warning")
> bbb24b6a681b ("Bluetooth: hci_sock: Correctly bounds check and pad HCI_MON_NEW_INDEX name")
These patches are now in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-19 21:24 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 3:14 linux-next: duplicate patches in the bluetooth tree Stephen Rothwell
2023-10-19 21:23 ` Stephen Rothwell [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-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-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=20231020082321.46af78d6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marcel@holtmann$(echo .)org \
/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