From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, soc@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Missing signoff in the arm-soc tree
Date: Mon, 14 Sep 2026 17:25:10 +0100 [thread overview]
Message-ID: <aqgf5o_gSUQH1AF0@sirena.co.uk> (raw)
In-Reply-To: <fd352f58-8100-4b0f-ac8c-25b08d0e2886@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
On Mon, Aug 03, 2026 at 06:25:57PM +0100, Mark Brown wrote:
> On Sun, Jul 26, 2026 at 05:29:00PM +0100, Mark Brown wrote:
> > Commit
> >
> > 3edcea7f0413e ("Merge branch 'arm/fixes' into for-next")
> >
> > is missing a Signed-off-by from its committer (and also isn't showing up
> > as a merge).
>
> This issue (and the matching author signoff) is still present today.
These issues are *still* present today. It's making noise whenever I
check -next for ongoing issues, it'd be good if the branch could be
rebuilt.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-14 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 16:29 Missing signoff in the arm-soc tree Mark Brown
2026-08-03 17:25 ` Mark Brown
2026-09-14 16:25 ` Mark Brown [this message]
2026-09-14 19:53 ` Arnd Bergmann
2026-09-14 23:08 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-07-26 16:28 Mark Brown
2026-07-13 17:35 Mark Brown
2026-07-13 17:38 ` Mark Brown
2026-07-15 11:39 ` Alexandre Belloni
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=aqgf5o_gSUQH1AF0@sirena.co.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=soc@lists.linux.dev \
/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