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:36:46 -0500 [thread overview]
Message-ID: <505A3AEE.8060408@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209192124570.5264@utopia.booyaka.com>
On 9/19/2012 4:26 PM, Paul Walmsley wrote:
> Hi Beno?t
>
> On Wed, 19 Sep 2012, Cousson, Benoit wrote:
>
>> 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
>>
>> Paul,
>> Is that OK?
>
> Looks to me like the clock change is unrelated to the DTS changes? Best
> thing would be if you could just take the DTS changes and I'll take the
> clkdev alias change.
Good point, it can be separated.
> Otherwise if that doesn't work I can ack it, but there might be some
> conflicts with other clkdev data changes.
No problem, that's fine for me.
Regards,
Benoit
next prev parent reply other threads:[~2012-09-19 21:36 UTC|newest]
Thread overview: 14+ 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 ` [PATCH RESEND v7 1/5] ARM: dts: AM33XX: Add basic pinctrl " 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 ` [PATCH RESEND 3/5] ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data AnilKumar Ch
2012-09-19 21:24 ` Paul Walmsley
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 ` [PATCH RESEND 5/5] ARM: dts: AM33XX: Add temperature sensor " AnilKumar Ch
2012-09-19 21:23 ` [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data Cousson, Benoit
2012-09-19 21:26 ` Paul Walmsley
2012-09-19 21:36 ` Cousson, Benoit [this message]
2012-09-19 21:28 ` AnilKumar, Chimata
2012-09-19 21:46 ` Cousson, Benoit
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=505A3AEE.8060408@ti.com \
--to=b-cousson@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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