From: Mark Brown <broonie@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Missing signoff in the bluetooth tree
Date: Mon, 28 Sep 2026 17:27:22 +0100 [thread overview]
Message-ID: <647ed0f5-360b-4d05-aaa9-9f3ade6f6b7f@sirena.org.uk> (raw)
In-Reply-To: <CABBYNZL_vs+_MudyOBDK+pBJtOYcEEE6snUhU_btwAuW0RTjDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Mon, Sep 28, 2026 at 11:13:19AM -0400, Luiz Augusto von Dentz wrote:
> Weird, this should have been fixed in the last back merge, going in
> the list of commits in bluetooth-next
> https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/log/
> they show as:
> commit c9c15d4d8956df8c564f7c210e4dc5b9b820d97a (gitolite-bluetooth/master)
> Author: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
> Date: Tue Sep 22 18:33:11 2026 +0530
>
> Bluetooth: btintel: validate DDC record lengths
I have this commit but also the older
4712bd9a14cbdd712fc8584f18be332b9ceb70b0 Bluetooth: btintel: validate DDC record lengths
I didn't spot check all the rest but there's a bunch of what look like
duplicated subjects. If you did a merge then both the fixed commits and
the original problematic commits will still be in the history.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-28 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 8:22 Mark Brown
2026-09-28 14:37 ` Mark Brown
2026-09-28 15:13 ` Luiz Augusto von Dentz
2026-09-28 16:27 ` Mark Brown [this message]
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=647ed0f5-360b-4d05-aaa9-9f3ade6f6b7f@sirena.org.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®