public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>, mturquette@linaro.org
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: pull request for Tegra clock rework and Tegra124 clock support
Date: Mon, 21 Oct 2013 20:57:42 +0100	[thread overview]
Message-ID: <52658736.6050707@wwwdotorg.org> (raw)
In-Reply-To: <20131021135638.GA10943@tbergstrom-lnx.Nvidia.com>

On 10/21/2013 02:56 PM, Peter De Schrijver wrote:
> Hi Mike,
> 
> This pull request contains both the tegra clock rework patches
> ([PATCH v6 00/15] Introduce common infra for tegra clocks)
> and the patches to support Tegra124 ([PATCH v4 0/7] Tegra124 clock support)
> 
> The following changes since commit d031acfc0b8376209e5b429513766e7028e40e1d:
> 
>   clk: tegra114: Rename gr_2d/gr_3d to gr2d/gr3d (2013-10-16 19:49:25 +0300)
> 
> are available in the git repository at:
>   git://nv-tegra.nvidia.com/user/pdeschrijver/linux.git tegra-clk-tegra124-0
> 
> Joseph Lo (2):
>       clk: tegra124: add wait_for_reset and disable_clock for tegra_cpu_car_ops
>       clk: tegra124: add suspend/resume function for tegra_cpu_car_ops

Acked-by: Stephen Warren <swarren@nvidia.com>


  reply	other threads:[~2013-10-21 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 13:56 pull request for Tegra clock rework and Tegra124 clock support Peter De Schrijver
2013-10-21 19:57 ` Stephen Warren [this message]
     [not found] ` <20131022101904.7554.73999@quantum>
2013-10-23  8:46   ` Peter De Schrijver
2013-10-30  0:47     ` Peter De Schrijver

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=52658736.6050707@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@linaro.org \
    --cc=pawel.moll@arm.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@nvidia.com \
    --cc=rob.herring@calxeda.com \
    --cc=thierry.reding@gmail.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