From: Peter Korsgaard <jacmet@sunsite.dk>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [PATCH RESEND] ARM: dts: AM33XX: Rename I2C and GPIO nodes
Date: Tue, 08 Jan 2013 10:30:45 +0100 [thread overview]
Message-ID: <8738ycaunu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EAD4863@DBDE01.ent.ti.com> (Chimata AnilKumar's message of "Wed, 2 Jan 2013 10:12:29 +0000")
>>>>> "AnilKumar" == AnilKumar, Chimata <anilkumar@ti.com> writes:
AnilKumar> On Wed, Nov 21, 2012 at 17:22:17, AnilKumar, Chimata wrote:
>> Rename I2C and GPIO nodes according to AM33XX TRM. According to
>> AM33XX TRM device instances are starting from "0" like i2c0, i2c1
>> and i2c3.
>>
>> Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com>
>> [panto@antoniou-consulting.com: initial patch by pantelis's]
>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>> ---
>> Changes from first version:
>> - Updated pantelis's patch
>> * Modified based on linux-omap/master
>> * Added GPIO nodes renaming as well
AnilKumar> Hi Tony/Benoit,
AnilKumar> If there are no comments could you please pull this patch?
Yes, please do.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-08 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 11:52 [PATCH RESEND] ARM: dts: AM33XX: Rename I2C and GPIO nodes AnilKumar Ch
[not found] ` <1353498737-21174-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-11-21 12:47 ` Peter Korsgaard
2013-01-02 10:12 ` AnilKumar, Chimata
2013-01-08 9:30 ` Peter Korsgaard [this message]
2013-01-08 16:13 ` Benoit Cousson
2013-01-09 9:41 ` Pantelis Antoniou
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=8738ycaunu.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=anilkumar@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=panto@antoniou-consulting.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