From: Stephen Warren <swarren@wwwdotorg.org>
To: Andrew Bresticker <abrestic@chromium.org>,
Mike Turquette <mturquette@linaro.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
linux-tegra@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/7] misc Tegra clock fixes
Date: Wed, 08 Jan 2014 15:41:02 -0700 [thread overview]
Message-ID: <52CDD3FE.1070404@wwwdotorg.org> (raw)
In-Reply-To: <CAL1qeaG0Y4__viWsZeoFdf8XFN3Wk7CO2abeEjzRZg+wNRV56w@mail.gmail.com>
On 01/08/2014 03:28 PM, Andrew Bresticker wrote:
> Hi Stephen, Peter,
>
>> Fixes for various clock-related issues found during bringup of
>> Tegra124-based Venice2 and Norrin boards.
...
> Any comments on this series?
Peter owns drivers/clk/tegra/, so I assume he'll handle these patches. I
briefly looked at them when they were posted and didn't see any issues.
next prev parent reply other threads:[~2014-01-08 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 0:44 [PATCH 0/7] misc Tegra clock fixes Andrew Bresticker
2013-12-27 0:44 ` [PATCH 1/7] clk: tegra: Fix PLLP rate table Andrew Bresticker
2013-12-27 0:44 ` [PATCH 2/7] clk: tegra: Fix PLLD mnp table Andrew Bresticker
2013-12-27 0:44 ` [PATCH 3/7] clk: tegra: PLLD2 fixes for hdmi Andrew Bresticker
2013-12-27 0:44 ` [PATCH 4/7] clk: tegra: fix host1x clock on Tegra124 Andrew Bresticker
2013-12-27 0:44 ` [PATCH 5/7] clk: tegra: fix sdmmc clks on Tegra1x4 Andrew Bresticker
2013-12-27 0:44 ` [PATCH 6/7] clk: tegra: cclk_lp has a pllx/2 divider Andrew Bresticker
2013-12-27 0:44 ` [PATCH 7/7] clk: tegra: use max divider if divider overflows Andrew Bresticker
2013-12-29 22:02 ` [PATCH 0/7] misc Tegra clock fixes Mike Turquette
2014-01-08 22:28 ` Andrew Bresticker
2014-01-08 22:41 ` Stephen Warren [this message]
2014-01-13 16:08 ` 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=52CDD3FE.1070404@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=abrestic@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.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