From: Rajendra Nayak <rnayak@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: devicetree@vger.kernel.org, "Tony Lindgren" <tony@atomide.com>,
linux-kernel@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 0/2] ARM: dts: OMAP2+: add i2c aliases
Date: Mon, 21 Oct 2013 14:48:00 +0530 [thread overview]
Message-ID: <5264F148.7030705@ti.com> (raw)
In-Reply-To: <1381954864-24410-1-git-send-email-nm@ti.com>
On Thursday 17 October 2013 01:51 AM, Nishanth Menon wrote:
> Add i2c aliases for OMAP and AM processor dts nodes to ensure proper
> i2c ordering. Based on Benoit's for_13/dts branch[1]
>
> Changes in V2:
> - Following Rajendra's suggestion, done for all OMAP and AM
> series SoCs, where i2c is defined.
Thanks Nishanth.
Acked-by: Rajendra Nayak <rnayak@ti.com>
>
> V1: https://patchwork.kernel.org/patch/3046671/
>
> Nishanth Menon (2):
> ARM: dts: OMAP3+: Add i2c aliases
> ARM: dts: AM33xx+: Add i2c aliases
>
> arch/arm/boot/dts/am33xx.dtsi | 3 +++
> arch/arm/boot/dts/am4372.dtsi | 3 +++
> arch/arm/boot/dts/dra7.dtsi | 5 +++++
> arch/arm/boot/dts/omap3.dtsi | 3 +++
> arch/arm/boot/dts/omap4.dtsi | 4 ++++
> arch/arm/boot/dts/omap5.dtsi | 5 +++++
> 6 files changed, 23 insertions(+)
>
> [1] https://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.13/dts
>
prev parent reply other threads:[~2013-10-21 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 17:00 [PATCH] ARM: dts: OMAP5: Add i2c aliases Nishanth Menon
2013-10-16 11:37 ` Rajendra Nayak
2013-10-16 12:58 ` Nishanth Menon
2013-10-16 20:21 ` [PATCH V2 0/2] ARM: dts: OMAP2+: add " Nishanth Menon
2013-10-16 20:21 ` [PATCH V2 1/2] ARM: dts: OMAP3+: Add " Nishanth Menon
2013-10-16 20:21 ` [PATCH V2 2/2] ARM: dts: AM33xx+: " Nishanth Menon
2013-10-21 9:18 ` Rajendra Nayak [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=5264F148.7030705@ti.com \
--to=rnayak@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@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 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).