From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Prashant Gaikwad
<pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] clk: tegra: Fix cdev1 and cdev2 IDs
Date: Thu, 04 Apr 2013 12:15:54 -0600 [thread overview]
Message-ID: <515DC35A.4030301@wwwdotorg.org> (raw)
In-Reply-To: <1365066304-2327-1-git-send-email-pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Correct IDs for cdev1 and cdev2 are 94 and 93 respectively.
This looks OK, but needs to be split up before I can apply it.
The binding change and driver changes will be applied to Tegra's
for-3.10/clk branch, since that's where clk changes are going.
The DT changes will be applied to Tegra's for-3.10/dt branch, since
that's where most of the DT content that's being edited here was
actually added, this kernel cycle.
There's no dependency between these two sets of changes, since the
clocks properties for the sound and USB PHY nodes aren't actually used
by the drivers yet; they're just being added this kernel cycle to avoid
dependencies in the next kernel version.
Mike, can you please ack this patch anyway, and I'll repost later in the
day when I get around to splitting it up and applying it. Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: Fix cdev1 and cdev2 IDs
Date: Thu, 04 Apr 2013 12:15:54 -0600 [thread overview]
Message-ID: <515DC35A.4030301@wwwdotorg.org> (raw)
In-Reply-To: <1365066304-2327-1-git-send-email-pgaikwad@nvidia.com>
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Correct IDs for cdev1 and cdev2 are 94 and 93 respectively.
This looks OK, but needs to be split up before I can apply it.
The binding change and driver changes will be applied to Tegra's
for-3.10/clk branch, since that's where clk changes are going.
The DT changes will be applied to Tegra's for-3.10/dt branch, since
that's where most of the DT content that's being edited here was
actually added, this kernel cycle.
There's no dependency between these two sets of changes, since the
clocks properties for the sound and USB PHY nodes aren't actually used
by the drivers yet; they're just being added this kernel cycle to avoid
dependencies in the next kernel version.
Mike, can you please ack this patch anyway, and I'll repost later in the
day when I get around to splitting it up and applying it. Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Prashant Gaikwad <pgaikwad@nvidia.com>, mturquette@linaro.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: Fix cdev1 and cdev2 IDs
Date: Thu, 04 Apr 2013 12:15:54 -0600 [thread overview]
Message-ID: <515DC35A.4030301@wwwdotorg.org> (raw)
In-Reply-To: <1365066304-2327-1-git-send-email-pgaikwad@nvidia.com>
On 04/04/2013 03:05 AM, Prashant Gaikwad wrote:
> Correct IDs for cdev1 and cdev2 are 94 and 93 respectively.
This looks OK, but needs to be split up before I can apply it.
The binding change and driver changes will be applied to Tegra's
for-3.10/clk branch, since that's where clk changes are going.
The DT changes will be applied to Tegra's for-3.10/dt branch, since
that's where most of the DT content that's being edited here was
actually added, this kernel cycle.
There's no dependency between these two sets of changes, since the
clocks properties for the sound and USB PHY nodes aren't actually used
by the drivers yet; they're just being added this kernel cycle to avoid
dependencies in the next kernel version.
Mike, can you please ack this patch anyway, and I'll repost later in the
day when I get around to splitting it up and applying it. Thanks.
next prev parent reply other threads:[~2013-04-04 18:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 9:05 [PATCH] clk: tegra: Fix cdev1 and cdev2 IDs Prashant Gaikwad
2013-04-04 9:05 ` Prashant Gaikwad
2013-04-04 9:05 ` Prashant Gaikwad
[not found] ` <1365066304-2327-1-git-send-email-pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-04-04 18:15 ` Stephen Warren [this message]
2013-04-04 18:15 ` Stephen Warren
2013-04-04 18:15 ` Stephen Warren
2013-04-04 23:27 ` Stephen Warren
2013-04-04 23:27 ` Stephen Warren
2013-04-04 23:27 ` Stephen Warren
-- strict thread matches above, loose matches on Subject: below --
2013-04-04 23:26 Stephen Warren
2013-04-04 23:26 ` Stephen Warren
[not found] ` <1365118019-5748-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-04-04 23:26 ` Stephen Warren
2013-04-04 23:26 ` Stephen Warren
2013-04-11 20:09 ` Mike Turquette
2013-04-11 20:09 ` Mike Turquette
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=515DC35A.4030301@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@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.