public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Vaibhav Hiremath <hvaibhav@ti.com>, paul@pwsan.com
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: AM33XX: clock: Add debugSS data to clk and hwmod database
Date: Tue, 18 Jun 2013 19:49:06 -0500	[thread overview]
Message-ID: <51C10002.5040301@ti.com> (raw)
In-Reply-To: <1371532080-27714-1-git-send-email-hvaibhav@ti.com>

Hi Vaibhav,

On 06/18/2013 12:07 AM, Vaibhav Hiremath wrote:
> This patch adds DebugSS data to clock-tree and hwmod data files.
>
> Changes from RFC/V1 (No code change):
> 	- Based on comments, we have to follow DT and loadable module
> 	  approach for debugSS module as well, so separated out 2 patches
> 	  of clock-tree and hwmod data addition from the RFC patch-series.
> 	- Added Paul's Ack on clock-tree patch.
> 	- Rebased on top of Benoit's for-3.11/dts branch.
>
> Link to original RFC -
> http://archive.arm.linux.org.uk/lurker/message/20130304.113554.53c9ec25.en.html
>
> Vaibhav Hiremath (2):
>    ARM: AM33XX: clock: Add debugSS clock nodes

I'll take that one, but the next one:

>    ARM: AM33XX: hwmod: Add hwmod data for debugSS

Still need to go through Paul's tree.

Paul,

Do you want to ack it, so I'll be able to take the whole series?

Thanks,
Benoit


  parent reply	other threads:[~2013-06-19  0:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18  5:07 [PATCH 0/2] ARM: AM33XX: clock: Add debugSS data to clk and hwmod database Vaibhav Hiremath
2013-06-18  5:07 ` [PATCH 1/2] ARM: AM33XX: clock: Add debugSS clock nodes Vaibhav Hiremath
2013-06-18  5:08 ` [PATCH 2/2] ARM: AM33XX: hwmod: Add hwmod data for debugSS Vaibhav Hiremath
2013-06-18  9:42 ` [PATCH 0/2] ARM: AM33XX: clock: Add debugSS data to clk and hwmod database Cousson, Benoit
2013-06-19  0:49 ` Benoit Cousson [this message]
2013-07-29  8:35   ` Paul Walmsley

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=51C10002.5040301@ti.com \
    --to=b-cousson@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox