From: Mark Brown <broonie@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Missing signoff in the bluetooth tree
Date: Wed, 23 Sep 2026 10:22:37 +0200 [thread overview]
Message-ID: <arOMTa0L7QhM5RyA@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Commits
4712bd9a14cbd ("Bluetooth: btintel: validate DDC record lengths")
7348abd83a3b2 ("Bluetooth: hci_core: free the HCI ID if naming fails")
ea983244b99a3 ("Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems")
2b036342b623c ("Bluetooth: btintel_pcie: reject oversized TX packets in send_frame()")
6d21e89e69775 ("Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame()")
4145a13c1a044 ("Bluetooth: btintel: fix buffer over-read in btintel_hw_error()")
are missing a Signed-off-by from their committers
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-09-23 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 8:22 Mark Brown [this message]
2026-09-28 14:37 ` Missing signoff in the bluetooth tree Mark Brown
2026-09-28 15:13 ` Luiz Augusto von Dentz
2026-09-28 16:27 ` Mark Brown
2026-09-28 17:03 ` Luiz Augusto von Dentz
2026-09-28 17:07 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-09-11 13:21 Mark Brown
2026-09-14 16:20 ` Mark Brown
2026-09-07 11:01 Mark Brown
2026-09-07 23:06 ` Mark Brown
2026-09-04 16:07 Mark Brown
2026-09-07 23:05 ` Mark Brown
2026-05-28 12:03 Mark Brown
2026-06-01 18:17 ` Mark Brown
2026-06-08 15:11 ` Mark Brown
2026-05-26 21:16 Mark Brown
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=arOMTa0L7QhM5RyA@sirena.co.uk \
--to=broonie@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.