From: Alan Ott <alan-yzvJWuRpmD1zbRFIqnYvSA@public.gmane.org>
To: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: Re: [PATCH v2 2/6] ARM: tegra: select CPU_FREQ_TABLE
Date: Sun, 04 Mar 2012 14:47:31 -0500 [thread overview]
Message-ID: <4F53C6D3.2060404@signal11.us> (raw)
In-Reply-To: <20120304183710.GB31064-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
On 3/4/12 1:37 PM, Olof Johansson wrote:
> On Fri, Mar 02, 2012 at 03:58:28PM -0500, Alan Ott wrote:
>> From: Arnd Bergmann<arnd-r2nGTMty4D4@public.gmane.org>
>>
>> The tegra cpufreq implementation relies on the cpu_freq_table
>> code, so make sure that this is always there when needed.
>>
>> Signed-off-by: Arnd Bergmann<arnd-r2nGTMty4D4@public.gmane.org>
>> Signed-off-by: Alan Ott<alan-yzvJWuRpmD1zbRFIqnYvSA@public.gmane.org>
>
> This didn't apply cleanly to the tegra tree (what was it based on?), but
> I fixed it up manually and applied to for-3.4/cleanups-and-fixes.
>
These were based on mainline.
Alan.
prev parent reply other threads:[~2012-03-04 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 20:58 [PATCH v2 2/6] ARM: tegra: select CPU_FREQ_TABLE Alan Ott
[not found] ` <1330721908-8633-1-git-send-email-alan-yzvJWuRpmD1zbRFIqnYvSA@public.gmane.org>
2012-03-04 18:37 ` Olof Johansson
[not found] ` <20120304183710.GB31064-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2012-03-04 19:47 ` Alan Ott [this message]
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=4F53C6D3.2060404@signal11.us \
--to=alan-yzvjwurpmd1zbrfiqnyvsa@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox