From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] omap device tree fixes for v3.14 merge window
Date: Tue, 14 Jan 2014 14:30:30 -0800 [thread overview]
Message-ID: <877ga26vsp.fsf@linaro.org> (raw)
In-Reply-To: <20140109012053.GJ31323@atomide.com> (Tony Lindgren's message of "Wed, 8 Jan 2014 17:20:54 -0800")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit adfe9361b236154215d4b0fc8b6d79995394b15c:
>
> ARM: dts: Add basic devices on am3517-evm (2013-12-08 14:15:46 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.14/dt-signed
>
> for you to fetch changes up to e37e1cb0ee231ffdc9b5ef1da63a0c7e1077c603:
>
> ARM: dts: OMAP2: fix interrupt number for rng (2014-01-08 10:24:44 -0800)
>
> ----------------------------------------------------------------
> Split omap3 core padconf area into two as some of the registers in
> the padconf area are not accessible and used for other devices.
> Also fix the interrupt number for omap2 RNG, and add basic support
> for sbc-3xxx with cm-t3730.
>
> Note that the minor merge conflicts for omap_hwmod_2xxx_ipblock_data.c
> can be solved by just dropping the legacy hwmod data for interrupts
> for v3.14.
>
> ----------------------------------------------------------------
Applying to next/fixes-non-critical.
Kevin
next prev parent reply other threads:[~2014-01-14 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 1:19 [GIT PULL 1/4] non-urgent omap fixes for v3.14 merge window Tony Lindgren
2014-01-09 1:20 ` [GIT PULL 2/4] omap device tree " Tony Lindgren
2014-01-14 22:30 ` Kevin Hilman [this message]
2014-01-09 1:21 ` [GIT PULL 3/4] trivial omap big endian changes " Tony Lindgren
2014-01-14 22:31 ` Kevin Hilman
2014-01-14 22:33 ` Tony Lindgren
2014-01-09 1:22 ` [GIT PULL 4/4] GIC crossbar support " Tony Lindgren
2014-01-14 22:40 ` 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=877ga26vsp.fsf@linaro.org \
--to=khilman@linaro.org \
--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).