From: Benoit Cousson <b-cousson@ti.com>
To: Anil Kumar <anilk4.v@gmail.com>
Cc: Jon Hunter <jon-hunter@ti.com>,
device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 0/8] ARM: dts: Various OMAP2+ device-tree updates
Date: Mon, 18 Mar 2013 11:14:15 +0100 [thread overview]
Message-ID: <5146E8F7.8080008@ti.com> (raw)
In-Reply-To: <CABYxbz5cW0Jt12SGcMpN5L0n18C6Mis0gRoBgSHWnxuAz6chGA@mail.gmail.com>
Hi Anil,
On 03/17/2013 10:35 AM, Anil Kumar wrote:
> Hi Benoit,
>
> On Fri, Mar 15, 2013 at 8:00 PM, Benoit Cousson <b-cousson@ti.com> wrote:
>> Hi Jon,
>>
>> On 03/15/2013 02:57 PM, Jon Hunter wrote:
>>> Various OMAP device-tree updates for PMU, DMA, GPIO, GPMC and boards.
>>>
>>> The DMA, PMU and OMAP3430 SDP board changes have been sent before
>>> individually but re-sending here as a complete series for v3.10.
>>>
>>> This is based upon Benoit's for_3.10/dts branch [1]. Branch available
>>> here [2].
>>>
>>> V2 changes:
>>> - Rebased on Benoit's for_3.10/dts branch
>>> - Squashed patches adding support for OMAP3430 SDP board and patch
>>> to add flash support for OMAP3430 SDP board.
>>>
>>> [1] http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
>>> [2] git://github.com/jonhunter/linux.git omap-dt-for-v3.10
>>
>> Thanks for the repost. I've just applied your branch in my for_3.10/dts
>> branch.
>
> I think you missed below patch which is needed for gpmc nand to work fine.
> Without this patch nand will not work on OMAP3430 SDP board.
>
> Jon Hunter:-
> ARM: OMAP2+: Fix-up gpmc merge error
Well, that patch is not part of Jon's series and it looks like it was
posted for 3.9-rc3.
BTW, Paul W is just reporting a regression about that patch.
Anyway, I'll rebase on top of -rc3 to get the latest fixes.
Regards,
Benoit
prev parent reply other threads:[~2013-03-18 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 13:57 [PATCH V2 0/8] ARM: dts: Various OMAP2+ device-tree updates Jon Hunter
2013-03-15 13:57 ` [PATCH V2 1/8] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2013-03-15 13:57 ` [PATCH V2 2/8] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2013-03-15 13:57 ` [PATCH V2 3/8] ARM: dts: OMAP2+: Add SDMA controller bindings and nodes Jon Hunter
2013-03-15 13:57 ` [PATCH V2 4/8] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5 Jon Hunter
2013-03-15 13:57 ` [PATCH V2 5/8] ARM: dts: Add OMAP2 gpio bindings Jon Hunter
2013-03-15 13:57 ` [PATCH V2 6/8] ARM: dts: OMAP3+: Correct gpio #interrupts-cells property Jon Hunter
2013-03-15 13:57 ` [PATCH V2 7/8] ARM: dts: OMAP3: Add reg and interrupt properties for gpio Jon Hunter
2013-03-15 13:57 ` [PATCH V2 8/8] ARM: dts: OMAP3: Add support for OMAP3430 SDP board Jon Hunter
2013-03-15 14:30 ` [PATCH V2 0/8] ARM: dts: Various OMAP2+ device-tree updates Benoit Cousson
2013-03-17 9:35 ` Anil Kumar
2013-03-18 10:14 ` Benoit Cousson [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=5146E8F7.8080008@ti.com \
--to=b-cousson@ti.com \
--cc=anilk4.v@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jon-hunter@ti.com \
--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).