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.17-rc cycle
Date: Fri, 20 Apr 2018 10:41:02 -0700	[thread overview]
Message-ID: <pull-1524246008-227018@atomide.com> (raw)

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

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)

are available in the Git repository at:

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

for you to fetch changes up to fb289e3ab10c16834741bb02be740fa9d025fde0:

  Merge branch 'omap-for-v4.17/fixes-ti-sysc' into omap-for-v4.17/fixes (2018-04-19 15:48:46 -0700)

----------------------------------------------------------------
Two fixes for v4.17-rc cycle

Fix a build regression with split object directories reported by Russell
and fix range sizes for omap4 cm2 and prm modules.

----------------------------------------------------------------
Dave Gerlach (1):
      ARM: OMAP2+: Fix build when using split object directories

Tony Lindgren (2):
      ARM: dts: Fix cm2 and prm sizes for omap4
      Merge branch 'omap-for-v4.17/fixes-ti-sysc' into omap-for-v4.17/fixes

 arch/arm/boot/dts/omap4.dtsi         |  8 ++--
 arch/arm/mach-omap2/Makefile         |  6 +--
 arch/arm/mach-omap2/pm-asm-offsets.c |  3 ++
 arch/arm/mach-omap2/sleep33xx.S      |  1 -
 arch/arm/mach-omap2/sleep43xx.S      |  1 -
 drivers/memory/emif-asm-offsets.c    | 72 +---------------------------------
 include/linux/ti-emif-sram.h         | 75 ++++++++++++++++++++++++++++++++++++
 7 files changed, 84 insertions(+), 82 deletions(-)

             reply	other threads:[~2018-04-20 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 17:41 Tony Lindgren [this message]
2018-04-26 14:54 ` [GIT PULL] two omap fixes for v4.17-rc cycle Arnd Bergmann

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-1524246008-227018@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).