From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] two omap fixes for v4.18-rc cycle
Date: Sat, 14 Jul 2018 15:14:39 -0700 [thread overview]
Message-ID: <20180714221439.jz6wujv6nxb6vzon@localhost> (raw)
In-Reply-To: <pull-1531484945-795802@atomide.com>
On Fri, Jul 13, 2018 at 05:29:53AM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 0144eb204cdcdf09a76794b4a294291388e739bc:
>
> ARM: dts: omap3: Fix am3517 mdio and emac clock references (2018-07-03 00:39:09 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.18/fixes-rc4-signed
>
> for you to fetch changes up to 923847413f7316b5ced3491769b3fefa6c56a79a:
>
> ARM: dts: am3517.dtsi: Disable reference to OMAP3 OTG controller (2018-07-12 06:57:05 -0700)
>
> ----------------------------------------------------------------
> Two omap fixes for v4.18-rc cycle
>
> Turns out the recent patches for ARM branch predictor hardening are
> not working on omap5 and dra7 as planned because the secondary CPU
> is parked to the bootrom code. We can't configure it in the bootloader.
> So we must enable invalidates of BTB for omap5 and dra7 secondary
> core in the kernel.
>
> And there's a fix for reserved register access for am3517. The
> usb otg module on am3517 is not the same as for other omap3.
Merged, thanks!
-Olof
prev parent reply other threads:[~2018-07-14 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 12:29 [GIT PULL] two omap fixes for v4.18-rc cycle Tony Lindgren
2018-07-14 22:14 ` Olof Johansson [this message]
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=20180714221439.jz6wujv6nxb6vzon@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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