From: "Cousson, Benoit" <b-cousson@ti.com>
To: "AnilKumar, Chimata" <anilkumar@ti.com>, Matt Porter <mporter@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
'paul Walmsley' <paul@pwsan.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data
Date: Wed, 19 Sep 2012 16:46:52 -0500 [thread overview]
Message-ID: <505A3D4C.4090502@ti.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA34232@DBDE01.ent.ti.com>
+ Matt
On 9/19/2012 4:28 PM, AnilKumar, Chimata wrote:
> On Thu, Sep 20, 2012 at 02:53:38, Cousson, Benoit wrote:
>> + Paul
>>
>> Hi Anil,
>>
>> Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
>> ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data
>>
What about Matt's series to fix the I2C number? Should it be applied on
top of that one?
Regards,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data
Date: Wed, 19 Sep 2012 16:46:52 -0500 [thread overview]
Message-ID: <505A3D4C.4090502@ti.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA34232@DBDE01.ent.ti.com>
+ Matt
On 9/19/2012 4:28 PM, AnilKumar, Chimata wrote:
> On Thu, Sep 20, 2012 at 02:53:38, Cousson, Benoit wrote:
>> + Paul
>>
>> Hi Anil,
>>
>> Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
>> ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data
>>
What about Matt's series to fix the I2C number? Should it be applied on
top of that one?
Regards,
Benoit
next prev parent reply other threads:[~2012-09-19 21:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 21:19 [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data AnilKumar Ch
2012-09-19 21:19 ` AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND v7 1/5] ARM: dts: AM33XX: Add basic pinctrl " AnilKumar Ch
2012-09-19 21:19 ` AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND v7 2/5] ARM: dts: AM33XX: Add D_CAN " AnilKumar Ch
2012-09-19 21:19 ` AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND 3/5] ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data AnilKumar Ch
2012-09-19 21:19 ` AnilKumar Ch
2012-09-19 21:24 ` Paul Walmsley
2012-09-19 21:24 ` Paul Walmsley
2012-09-19 21:27 ` AnilKumar, Chimata
2012-09-19 21:27 ` AnilKumar, Chimata
2012-09-19 21:19 ` [PATCH RESEND v3 4/5] ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm AnilKumar Ch
2012-09-19 21:19 ` AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND 5/5] ARM: dts: AM33XX: Add temperature sensor " AnilKumar Ch
2012-09-19 21:19 ` AnilKumar Ch
2012-09-19 21:23 ` [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data Cousson, Benoit
2012-09-19 21:23 ` Cousson, Benoit
2012-09-19 21:26 ` Paul Walmsley
2012-09-19 21:26 ` Paul Walmsley
2012-09-19 21:36 ` Cousson, Benoit
2012-09-19 21:36 ` Cousson, Benoit
2012-09-19 21:28 ` AnilKumar, Chimata
2012-09-19 21:28 ` AnilKumar, Chimata
2012-09-19 21:46 ` Cousson, Benoit [this message]
2012-09-19 21:46 ` Cousson, Benoit
2012-09-28 20:48 ` Matt Porter
2012-09-28 20:48 ` Matt Porter
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=505A3D4C.4090502@ti.com \
--to=b-cousson@ti.com \
--cc=anilkumar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=paul@pwsan.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.