From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] ARM: tegra: common clock framework fixes
Date: Tue, 19 Feb 2013 21:43:58 +0000 [thread overview]
Message-ID: <201302192143.59019.arnd@arndb.de> (raw)
In-Reply-To: <1360780358-2866-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Wednesday 13 February 2013, Stephen Warren wrote:
> A number of small fixes are included to the new Tegra common clock
> driver. These are: Missing locking, definition of device tree clock IDs
> not matching the binding, a static cleanup, missing initialization of
> some UART clocks.
>
> This branch is based on Tegra's previous pull request tegra-for-3.9-dt.
> This dependency is caused by the one patch that edits the device tree.
> If this causes a problem, I can drop the final two patches in this pull
> request for now, and rebase it onto previous tegra-for-3.9-soc-ccf
> instead.
It's not ideal, but I've merged them into next/dt now because of this
dependency. The order of the next/* branches in arm-soc is fixed
now because of other dependencies, so putting it into next/soc would
have been equally wrong.
I think a better solution would have been to send two pull requests,
where one was based on the ccf branch and the other on the dt branch.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: tegra: common clock framework fixes
Date: Tue, 19 Feb 2013 21:43:58 +0000 [thread overview]
Message-ID: <201302192143.59019.arnd@arndb.de> (raw)
In-Reply-To: <1360780358-2866-1-git-send-email-swarren@wwwdotorg.org>
On Wednesday 13 February 2013, Stephen Warren wrote:
> A number of small fixes are included to the new Tegra common clock
> driver. These are: Missing locking, definition of device tree clock IDs
> not matching the binding, a static cleanup, missing initialization of
> some UART clocks.
>
> This branch is based on Tegra's previous pull request tegra-for-3.9-dt.
> This dependency is caused by the one patch that edits the device tree.
> If this causes a problem, I can drop the final two patches in this pull
> request for now, and rebase it onto previous tegra-for-3.9-soc-ccf
> instead.
It's not ideal, but I've merged them into next/dt now because of this
dependency. The order of the next/* branches in arm-soc is fixed
now because of other dependencies, so putting it into next/soc would
have been equally wrong.
I think a better solution would have been to send two pull requests,
where one was based on the ccf branch and the other on the dt branch.
Arnd
next prev parent reply other threads:[~2013-02-19 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 18:32 [GIT PULL] ARM: tegra: common clock framework fixes Stephen Warren
2013-02-13 18:32 ` Stephen Warren
[not found] ` <1360780358-2866-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-19 21:43 ` Arnd Bergmann [this message]
2013-02-19 21:43 ` Arnd Bergmann
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=201302192143.59019.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.