From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] SoC changes for omaps for v5.8
Date: Wed, 13 May 2020 09:35:43 -0700 [thread overview]
Message-ID: <pull-1589387719-605999@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.8/soc-signed-take2
for you to fetch changes up to d33e3d542b6c09a5cb4fa51d82109b2ca92e89c2:
ARM: OMAP2+: pm33xx-core: Make am43xx_get_rtc_base_addr static (2020-05-12 08:36:04 -0700)
----------------------------------------------------------------
SoC changes for omaps for v5.8 merge window
SoC related changes for omaps:
- Use ard instead of adrl for sleep34xx.S for clang
- Stop selecting MIGHT_HAVE_CACHE_L2X0, it's already selected
by ARCH_MULTI_V6_V7
- Make omap5_erratum_workaround_801819() and am43xx_get_rtc_base_addr()
static
----------------------------------------------------------------
Geert Uytterhoeven (1):
ARM: omap2plus: Drop unneeded select of MIGHT_HAVE_CACHE_L2X0
Ma Feng (1):
ARM: omap2: make omap5_erratum_workaround_801819 static
Samuel Zou (1):
ARM: OMAP2+: pm33xx-core: Make am43xx_get_rtc_base_addr static
Stefan Agner (1):
ARM: OMAP2+: drop unnecessary adrl
arch/arm/mach-omap2/Kconfig | 1 -
arch/arm/mach-omap2/omap-smp.c | 2 +-
arch/arm/mach-omap2/pm33xx-core.c | 2 +-
arch/arm/mach-omap2/sleep34xx.S | 2 +-
4 files changed, 3 insertions(+), 4 deletions(-)
reply other threads:[~2020-05-13 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pull-1589387719-605999@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.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;
as well as URLs for NNTP newsgroup(s).