From: Sricharan R <r.sricharan@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, tony@atomide.com,
rnayak@ti.com
Subject: Re: [PATCH V2 0/4] ARM: dts: omap5: Cleanup and updates for DT files
Date: Fri, 7 Jun 2013 18:57:17 +0530 [thread overview]
Message-ID: <51B1DFB5.7080701@ti.com> (raw)
In-Reply-To: <51B1CCBD.5080904@ti.com>
On Friday 07 June 2013 05:36 PM, Benoit Cousson wrote:
> On 06/06/2013 07:48 PM, Sricharan R wrote:
>> uevm is the official board supported for OMAP5 soc in the mainline.
>> This series renames the board dts file for OMAP5 accordingly and cleans
>> up the same. Also a few additional device DT entry updates are done.
>>
>> This is on top of the below branch
>> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
>> for_3.11/dts
> Could you update your branch before reposting, I pulled a Makefile fix
> for AM5xx that prevents your patches to be applied properly.
Ok, rebased and posted V3.
Regards,
Sricharan
WARNING: multiple messages have this Message-ID (diff)
From: r.sricharan@ti.com (Sricharan R)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/4] ARM: dts: omap5: Cleanup and updates for DT files
Date: Fri, 7 Jun 2013 18:57:17 +0530 [thread overview]
Message-ID: <51B1DFB5.7080701@ti.com> (raw)
In-Reply-To: <51B1CCBD.5080904@ti.com>
On Friday 07 June 2013 05:36 PM, Benoit Cousson wrote:
> On 06/06/2013 07:48 PM, Sricharan R wrote:
>> uevm is the official board supported for OMAP5 soc in the mainline.
>> This series renames the board dts file for OMAP5 accordingly and cleans
>> up the same. Also a few additional device DT entry updates are done.
>>
>> This is on top of the below branch
>> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
>> for_3.11/dts
> Could you update your branch before reposting, I pulled a Makefile fix
> for AM5xx that prevents your patches to be applied properly.
Ok, rebased and posted V3.
Regards,
Sricharan
next prev parent reply other threads:[~2013-06-07 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 17:48 [PATCH V2 0/4] ARM: dts: omap5: Cleanup and updates for DT files Sricharan R
2013-06-06 17:48 ` Sricharan R
2013-06-06 17:48 ` [PATCH V2 1/4] ARM: dts: omap5: Rename omap5-evm to omap5-uevm Sricharan R
2013-06-06 17:48 ` Sricharan R
2013-06-07 12:03 ` Benoit Cousson
2013-06-07 12:03 ` Benoit Cousson
2013-06-07 13:27 ` Sricharan R
2013-06-07 13:27 ` Sricharan R
2013-06-06 17:48 ` [PATCH V2 2/4] ARM: dts: omap5-uevm: Add USB Host support Sricharan R
2013-06-06 17:48 ` Sricharan R
2013-06-06 17:48 ` [PATCH V2 3/4] ARM: dts: omap5-uevm: Add LED support for uEVM blue LED Sricharan R
2013-06-06 17:48 ` Sricharan R
2013-06-06 17:48 ` [PATCH V2 4/4] ARM: dts: omap5-uevm: Add uart pinctrl data Sricharan R
2013-06-06 17:48 ` Sricharan R
2013-06-07 12:06 ` [PATCH V2 0/4] ARM: dts: omap5: Cleanup and updates for DT files Benoit Cousson
2013-06-07 12:06 ` Benoit Cousson
2013-06-07 13:27 ` Sricharan R [this message]
2013-06-07 13:27 ` Sricharan R
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=51B1DFB5.7080701@ti.com \
--to=r.sricharan@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.