linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP AM33XX: clock data: Enable clkout2 output on SoC pad
Date: Mon, 27 May 2013 14:27:15 +0200	[thread overview]
Message-ID: <51A35123.6040600@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1305200246080.2656@utopia.booyaka.com>

Salut Paul,

On 05/20/2013 04:47 AM, Paul Walmsley wrote:
> On Fri, 17 May 2013, Hiremath, Vaibhav wrote:
> 
>> Tony, Paul and Benoit,
>>
>> Any update on this series?
> 
> Most of the changes are DT-related, so it should probably go in via 
> Beno?t.  I'll ack the clock side, but have a comment on patch 2, to be 
> sent shortly.

I've tried to apply that patch, but unfortunately, it does depend on
that one:

https://patchwork.kernel.org/patch/2212081/

If you did not already pulled the first one I can take both with your
acked-by.
Otherwise, I can take only the DTS ones.

Is that OK?

Thanks,
Benoit

  parent reply	other threads:[~2013-05-27 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  9:39 [PATCH 0/2] ARM: OMAP AM33XX: clock data: Enable clkout2 output on SoC pad Vaibhav Hiremath
2013-05-07  9:39 ` [PATCH 1/2] ARM: OMAP AM33XX: clock data: Enable clkout2 as part of init Vaibhav Hiremath
2013-05-20  2:50   ` Paul Walmsley
2013-05-20  5:30     ` Hiremath, Vaibhav
2013-05-07  9:39 ` [PATCH 2/2] ARM: dts: AM33XX: Set pinmux for clkout2 pad used for clock output Vaibhav Hiremath
2013-05-20  2:51   ` Paul Walmsley
2013-05-20  5:30     ` Hiremath, Vaibhav
2013-05-17 11:07 ` [PATCH 0/2] ARM: OMAP AM33XX: clock data: Enable clkout2 output on SoC pad Hiremath, Vaibhav
2013-05-20  2:47   ` Paul Walmsley
2013-05-20  5:31     ` Hiremath, Vaibhav
2013-05-27 12:27     ` Benoit Cousson [this message]
2013-05-29 19:06       ` Paul Walmsley
2013-06-03 12:35         ` Benoit Cousson

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=51A35123.6040600@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).