From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [v2 0/6] CLK: tegra: convert device tree files to use CLK defines
Date: Tue, 21 May 2013 10:05:49 -0600 [thread overview]
Message-ID: <519B9B5D.4050402@wwwdotorg.org> (raw)
In-Reply-To: <1369127450-15203-1-git-send-email-hdoyu@nvidia.com>
On 05/21/2013 03:10 AM, Hiroshi Doyu wrote:
> This patchset converts device tree files to use CLK defines. This
> version was updated along with the latest DT changes.
>
> The following changes since commit 7479d8bb5650f43053d0e82fa44db668cf968f11:
>
> TESTING: Build Tegra USB as a module (2013-05-20 13:11:19 -0600)
That commit is in my personal work-in-progress branch. This series
should be based on Tegra's for-3.11/dt branch. This will make a
difference (at least) in patch 6/6, where you've edited some DT nodes
that don't yet exist upstream (i.e. Tegra's for-3.11/dt branch) and
hence this series won't apply there.
I assume you're planning to send a series for 3.11 that converts
drivers/clk/tegra/ to use these new header files?
If so, I'll need to apply patches 1, 3, 5 to a separate branch, so it
can be pulled into the branch where the drivers/clk changes are applied,
then apply patches 2, 4, 6 to Tegra's for-3.11/dt after merging in the
branch with the header files.
next prev parent reply other threads:[~2013-05-21 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 9:10 [v2 0/6] CLK: tegra: convert device tree files to use CLK defines Hiroshi Doyu
2013-05-21 16:05 ` Stephen Warren [this message]
2013-05-22 6:12 ` Hiroshi Doyu
2013-05-22 10:07 ` Hiroshi Doyu
2013-05-22 15:20 ` Stephen Warren
2013-05-22 15:19 ` Stephen Warren
[not found] ` <1369127450-15203-3-git-send-email-hdoyu@nvidia.com>
2013-05-21 16:13 ` [v2 2/6] ARM: tegra20: " Stephen Warren
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=519B9B5D.4050402@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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