From: Tony Lindgren <tony@atomide.com>
To: arm@kernel.org
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for v4.6-rc cycle
Date: Thu, 28 Apr 2016 07:50:48 -0700 [thread overview]
Message-ID: <20160428145047.GE5995@atomide.com> (raw)
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.6/fixes-rc5-signed
for you to fetch changes up to 7472931f7f1e9d91f761dce30107ae345b61a5c3:
ARM: dts: omap5: fix range of permitted wakeup pinmux registers (2016-04-26 10:16:12 -0700)
----------------------------------------------------------------
Fixes for omaps for v4.6-rc cycle. All dts fixes, mostly
affecting voltages and pinctrl for various device drivers:
- Regulator minimum voltage fixes for omap5
- ISP syscon register offset fix for omap3
- Fix regulator initial modes for n900
- Fix omap5 pinctrl wkup instance size
----------------------------------------------------------------
H. Nikolaus Schaller (1):
ARM: dts: omap5: fix range of permitted wakeup pinmux registers
Ivaylo Dimitrov (2):
ARM: dts: omap3: Fix ISP syscon register offset
ARM: dts: omap3-n900: Specify peripherals LDO regulators initial mode
Tomi Valkeinen (2):
ARM: dts: omap5-board-common: fix ldo1_reg and ldo4_reg ranges
ARM: dts: omap5-cm-t54: fix ldo1_reg and ldo4_reg ranges
arch/arm/boot/dts/omap3-n900.dts | 9 +++++++++
arch/arm/boot/dts/omap34xx.dtsi | 2 +-
arch/arm/boot/dts/omap5-board-common.dtsi | 4 ++--
arch/arm/boot/dts/omap5-cm-t54.dts | 4 ++--
arch/arm/boot/dts/omap5.dtsi | 2 +-
5 files changed, 15 insertions(+), 6 deletions(-)
next reply other threads:[~2016-04-28 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 14:50 Tony Lindgren [this message]
2016-04-28 15:46 ` [GIT PULL] omap fixes for v4.6-rc cycle Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2016-04-14 20:36 Tony Lindgren
2016-04-23 0:21 ` Kevin Hilman
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=20160428145047.GE5995@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.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).