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: Wed, 22 May 2013 09:20:04 -0600 [thread overview]
Message-ID: <519CE224.3010107@wwwdotorg.org> (raw)
In-Reply-To: <20130522.130730.1153046210420942555.hdoyu@nvidia.com>
On 05/22/2013 04:07 AM, Hiroshi Doyu wrote:
> Hiroshi Doyu <hdoyu@nvidia.com> wrote @ Wed, 22 May 2013 08:12:48 +0200:
>
>> On Tue, 21 May 2013 18:05:49 +0200
>> Stephen Warren <swarren@wwwdotorg.org> wrote:
>>
>>> 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'll rebase.
>
> Rebased on Tegra's for-3.11/dt, including fix: [2/6] over 80 columns.
>
> If you want me to send patches again, please let me know.
Yes, you should always send the patches for review on mailing lists.
next prev parent reply other threads:[~2013-05-22 15:20 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
2013-05-22 6:12 ` Hiroshi Doyu
2013-05-22 10:07 ` Hiroshi Doyu
2013-05-22 15:20 ` Stephen Warren [this message]
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=519CE224.3010107@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).