Re: Missing signoff in the bluetooth tree

[Luiz Augusto von Dentz]

Hi Mark,

On Mon, Sep 28, 2026 at 12:27 PM Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> 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@xxxxxxxxx>
> > 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.

Interesting, so back merges seem particularly weak regarding
duplicates. I wonder if there is a merge option that can eliminate
duplicates, since I don't think there is any value in keeping previous
ids if a new merge changes them.

-- 
Luiz Augusto von Dentz