linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] two omap fixes for v4.16-rc cycle
Date: Fri, 16 Mar 2018 08:37:35 -0700	[thread overview]
Message-ID: <pull-1521214629-131951@atomide.com> (raw)

From: "Tony Lindgren" <tony@atomide.com>

The following changes since commit d39b6ea4f8c90e9e5f03a06b6a4fd4af11e2f617:

  bus: ti-sysc: Fix checking of no-reset-on-init quirk (2018-02-15 09:18:55 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.16/fixes-rc5-signed

for you to fetch changes up to 4e1e720009a78a7057a142de47def1e9f4bf41c7:

  ARM: OMAP: Fix SRAM W+X mapping (2018-03-08 10:28:46 -0800)

----------------------------------------------------------------
Two fixes for omap variants for v4.16-rc cycle

Fix insecure W+X mapping warning for SRAM for omaps that
don't yet use drivers/misc/*sram*.c code.

Also fix dmtimer probe for omap16xx devices that was noticed
with the pending dmtimer move to drivers. It seems this has
been broken for a while and is a non-critical for booting.
It is needed for PM on omap16xx though.

----------------------------------------------------------------
Tony Lindgren (3):
      ARM: OMAP: Fix dmtimer init for omap1
      Merge branch 'omap-for-v.16/dmtimer-fix' into omap-for-v4.16/fixes
      ARM: OMAP: Fix SRAM W+X mapping

 arch/arm/plat-omap/dmtimer.c |  7 ++-----
 arch/arm/plat-omap/sram.c    | 19 +++++++++++++++++++
 2 files changed, 21 insertions(+), 5 deletions(-)

             reply	other threads:[~2018-03-16 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 15:37 Tony Lindgren [this message]
2018-03-20 20:57 ` [GIT PULL] two omap fixes for v4.16-rc cycle Tony Lindgren

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-1521214629-131951@atomide.com \
    --to=tony@atomide.com \
    --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;
as well as URLs for NNTP newsgroup(s).