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: Missing signoff in the arm-soc tree
Date: Mon, 13 Jul 2026 18:35:55 +0100 [thread overview]
Message-ID: <alUh--gXbJNcbmuV@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Commits
923588dd861ba ("ARM: mark mv78xx0 support as deprecated")
3a09d8c6b3688 ("ARM: mark axxia platform as deprecated")
fa431f73cc18a ("ARM: mark Cortex-M3/M4/M7 based boards as deprecated")
fd0148ccd1d8f ("ARM: mark footbridge as deprecated")
faae50ff70799 ("ARM: mark RiscPC as deprecated")
25592ecf80a17 ("ARM: mark mach-sa1100 as deprecated")
7a9d2a5cb68f4 ("ARM: orion5x: mark all board files as deprecated")
a28d72f93f209 ("ARM: PXA: mark remaining board files as deprecated")
bb09fdba36e19 ("ARM: mark ARCH_DOVE as deprecated")
337de957c1166 ("ARM: mark IWMMXT as deprecated")
09b6757da5976 ("ARM: update FPE_NWFPE help text")
8b0e28c2792ec ("ARM: s3c64xx: extend deprecation schedule")
ef53a06103114 ("ARM: update DEPRECATED_PARAM_STRUCT removal timeline")
ed1dab5e08938 ("ARM: mark CPU_ENDIAN_BE8 as deprecated")
4d9226b820c16 ("ARM: turn CONFIG_ATAGS off by default")
e61f27ee54497 ("ARM: deprecate support for ARM1136r0")
07c06fe4622bb ("ARM: rework ARM11 CPU selection logic")
a82f541ab97f0 ("ARM: limit OABI support to StrongARM CPUs")
4122589d5488c ("ARM: use CONFIG_AEABI by default everywhere")
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-07-13 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 17:35 Mark Brown [this message]
2026-07-13 17:38 ` Missing signoff in the arm-soc tree 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=alUh--gXbJNcbmuV@sirena.org.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