From: Mike Turquette <mturquette@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Simon Glass <sjg@chromium.org>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9b 10/14] ARM: tegra: Define Tegra114 CAR binding
Date: Mon, 08 Apr 2013 21:25:37 -0700 [thread overview]
Message-ID: <20130409042537.14359.94241@quantum> (raw)
In-Reply-To: <515DBE24.3090501@wwwdotorg.org>
Quoting Stephen Warren (2013-04-04 10:53:40)
> On 04/04/2013 11:48 AM, Peter De Schrijver wrote:
> > The device tree binding models Tegra114 CAR (Clock And Reset) as a single
> > monolithic clock provider.
> >
> > --
> >
> > Mike,
> >
> > This is a small binding doc update only. Hence I didn't make an entire new
> > patch series, but just an updated version of this patch. Please apply this
> > instead of '[PATCH v9 10/14] ARM: tegra: Define Tegra114 CAR binding'
> > (http://www.spinics.net/lists/linux-tegra/msg10910.html).
> > The rest of the series is not affected.
>
> I believe I was planning to take this series through the Tegra tree, so
> I'm more looking for Mikes ack than for him to apply this.
>
> If that's changed, there are some other Tegra clock bug-fixes that'd
> benefit from moving to the clock tree.
I forgot to reply to this one last week with the rest of the v9 series.
This patch update also has my ack.
Regards,
Mike
prev parent reply other threads:[~2013-04-09 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:48 [PATCH v9b 10/14] ARM: tegra: Define Tegra114 CAR binding Peter De Schrijver
2013-04-04 17:53 ` Stephen Warren
2013-04-09 4:25 ` Mike Turquette [this message]
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=20130409042537.14359.94241@quantum \
--to=mturquette@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sjg@chromium.org \
--cc=swarren@wwwdotorg.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