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: linux-next: duplicate patches in the bluetooth tree
Date: Fri, 1 Mar 2024 09:25:39 +1100 [thread overview]
Message-ID: <20240301092539.584c26b7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
2d958ee64d5e ("Bluetooth: qca: Fix triggering coredump implementation")
30a746ee2438 ("Bluetooth: Enforce validation on max value of connection interval")
464f888b0534 ("Bluetooth: hci_sync: Check the correct flag before starting a scan")
5197b25a3803 ("Bluetooth: hci_sync: Fix accept_list when attempting to suspend")
51fda2df0c7a ("Bluetooth: mgmt: Fix limited discoverable off timeout")
571dd44ebd09 ("Bluetooth: hci_event: Fix wrongly recorded wakeup BD_ADDR")
5befbb8e4260 ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")
83fd7383955f ("Bluetooth: hci_bcm4377: do not mark valid bd_addr as invalid")
b44647f271b1 ("Bluetooth: Avoid potential use-after-free in hci_error_reset")
c64e95bdf43b ("Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security")
dae9093faed4 ("Bluetooth: qca: Fix wrong event type for patch config command")
e8aacc745769 ("Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-29 22:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 22:25 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-13 0:53 linux-next: duplicate patches in the bluetooth tree 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
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=20240301092539.584c26b7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=johan.hedberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcel@holtmann.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 read-only IMAP folder(s) and NNTP newsgroup(s).