From: Jon Hunter <jon-hunter@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH V3 0/2] arm/dts: Add OMAP2420 SDP support
Date: Tue, 12 Jun 2012 19:23:55 -0500 [thread overview]
Message-ID: <4FD7DD9B.40706@ti.com> (raw)
In-Reply-To: <4FD7DB2C.3090208@ti.com>
On 06/12/2012 07:13 PM, Jon Hunter wrote:
>
> On 06/12/2012 07:10 PM, Jon Hunter wrote:
>> This series fixes the OMAP2 interrupt controller binding and adds support for
>> the OMAP2420H4 board. I have verified that the kernel boots with device-tree
>> on this board.
>
> Oops! Forgot to change SDP to H4 in the $SUBJECT. However, should be
> correct elsewhere.
Ok, scratch this version. I have forgotten to change the dts file too.
Sorry for all the noise, I shouldn't be trying to cram this in at the
end of the day!
Jon
>> This series is based upon the linux-omap master branch (3.5-rc1).
>>
>> V3: Rename OMAP2420 SDP to OMAP2420H4
>> V2: Correct typo in copyright date
>>
>> Jon Hunter (2):
>> arm/dts: OMAP2: Add support for OMAP2420H4 Board
>> arm/dts: OMAP2: Fix interrupt controller binding
>>
>> arch/arm/boot/dts/omap2.dtsi | 2 ++
>> arch/arm/boot/dts/omap2420-sdp.dts | 20 ++++++++++++++++++++
>> 2 files changed, 22 insertions(+)
>> create mode 100644 arch/arm/boot/dts/omap2420-sdp.dts
>>
prev parent reply other threads:[~2012-06-13 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 0:10 [PATCH V3 0/2] arm/dts: Add OMAP2420 SDP support Jon Hunter
2012-06-13 0:10 ` [PATCH V3 1/2] arm/dts: OMAP2: Add support for OMAP2420H4 Board Jon Hunter
2012-06-13 0:10 ` [PATCH V3 2/2] arm/dts: OMAP2: Fix interrupt controller binding Jon Hunter
2012-06-13 0:13 ` [PATCH V3 0/2] arm/dts: Add OMAP2420 SDP support Jon Hunter
2012-06-13 0:23 ` Jon Hunter [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=4FD7DD9B.40706@ti.com \
--to=jon-hunter@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).