From: Arnd Bergmann <arnd@kernel.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
Robert Jarzmik <robert.jarzmik@free.fr>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH 0/3] ARM: SoC fixes
Date: Mon, 9 Jan 2023 17:16:33 +0100 [thread overview]
Message-ID: <20230109161636.512203-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
These are three fixes for mistakes I discovered during the preparation
of the boardfile removal. Robert noticed the accidental removal
of PXA310 and PXA320 support because of a misplaced Kconfig statement,
and the two OMAP patches were build failures that got introduced
earlier but that I found while testing the removal.
If these look fine, I'll queue them for 6.2 and for stable backports,
basing the boardfile removal patches on top.
Arnd Bergmann (3):
ARM: pxa: enable PXA310/PXA320 for DT-only build
ARM: omap1: fix !ARCH_OMAP1_ANY link failures
ARM: omap1: fix building gpio15xx
arch/arm/mach-omap1/Kconfig | 5 +----
arch/arm/mach-omap1/Makefile | 4 ----
arch/arm/mach-omap1/gpio15xx.c | 1 +
arch/arm/mach-omap1/io.c | 32 +++++++++++++++-----------------
arch/arm/mach-omap1/mcbsp.c | 21 ---------------------
arch/arm/mach-omap1/pm.h | 7 -------
arch/arm/mach-pxa/Kconfig | 2 ++
include/linux/soc/ti/omap1-io.h | 4 ++--
8 files changed, 21 insertions(+), 55 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-09 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 16:16 Arnd Bergmann [this message]
2023-01-09 16:16 ` [PATCH 1/3] ARM: pxa: enable PXA310/PXA320 for DT-only build Arnd Bergmann
2023-01-23 15:30 ` Robert Jarzmik
2023-01-09 16:16 ` [PATCH 2/3] ARM: omap1: fix !ARCH_OMAP1_ANY link failures Arnd Bergmann
2023-01-10 21:14 ` Aaro Koskinen
2023-01-09 16:16 ` [PATCH 3/3] ARM: omap1: fix building gpio15xx Arnd Bergmann
2023-01-10 21:15 ` Aaro Koskinen
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=20230109161636.512203-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jmkrzyszt@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).