From: Arnd Bergmann <arnd@arndb.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, arvind.chauhan@arm.com
Subject: Re: [PATCH 00/11] CPUFreq Kconfig fixes
Date: Wed, 12 Jun 2013 16:49:41 +0200 [thread overview]
Message-ID: <201306121649.41656.arnd@arndb.de> (raw)
In-Reply-To: <CAKohpont-8ZNDWx0n1G8ks=evfoJi3kQ5idjmeguyT8BWgTY4w@mail.gmail.com>
On Wednesday 12 June 2013, Viresh Kumar wrote:
>
> On 12 June 2013 18:16, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Wednesday 12 June 2013, Viresh Kumar wrote:
> >> Recently Arnd sent few fixes where drivers were using APIs from freq_table.c but
> >> haven't selected CPU_FREQ_TABLE. Based on that, I just crossed checked all the
> >> places where it should be selected and where it shouldn't be. These are fixes
> >> around that.
> >>
> >> I have applied these in my cpufreq-kconfig-fixes branch. Will send you a pull
> >> request separately once I get some Acks (will wait for few days).
> >
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
> >
> > I don't see a patch for big.LITTLE in either linux-next or this series. Did you
> > miss that or has it just not made into linux-next yet?
>
> My ARM branch was pulled in by Rafael, 2 days back. Don't know why didn't
> you saw that.
Ah, it seems we haven't had a new linux-next since friday.
Arnd
next prev parent reply other threads:[~2013-06-12 14:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 8:15 [PATCH 00/11] CPUFreq Kconfig fixes Viresh Kumar
2013-06-12 8:15 ` [PATCH 01/11] cpufreq: blackfin: enable driver for CONFIG_BFIN_CPU_FREQ Viresh Kumar
2013-06-17 4:39 ` [uclinux-dist-devel] " Mike Frysinger
2013-06-12 8:15 ` [PATCH 02/11] cpufreq: cris: select CPU_FREQ_TABLE Viresh Kumar
2013-06-12 8:15 ` [PATCH 03/11] cpufreq: davinci: " Viresh Kumar
2013-06-12 8:15 ` [PATCH 04/11] cpufreq: exynos: " Viresh Kumar
2013-06-12 8:15 ` [PATCH 05/11] cpufreq: highbank: remove " Viresh Kumar
2013-06-12 17:04 ` Mark Langsdorf
2013-06-12 8:15 ` [PATCH 06/11] cpufreq: imx: " Viresh Kumar
2013-06-12 11:38 ` Shawn Guo
2013-06-12 8:15 ` [PATCH 07/11] cpufreq: powerpc: CBE_RAS: " Viresh Kumar
2013-06-12 8:15 ` [PATCH 08/11] cpufreq: pxa: " Viresh Kumar
2013-06-12 8:15 ` [PATCH 09/11] cpufreq: S3C2416/S3C64XX: " Viresh Kumar
2013-06-12 9:11 ` Heiko Stübner
2013-06-12 8:15 ` [PATCH 10/11] cpufreq: tegra: select CPU_FREQ_TABLE for ARCH_TEGRA Viresh Kumar
2013-06-12 15:50 ` Stephen Warren
2013-06-13 4:24 ` Viresh Kumar
2013-06-13 15:43 ` Stephen Warren
2013-06-13 15:46 ` Viresh Kumar
2013-06-12 8:15 ` [PATCH 11/11] cpufreq: X86_AMD_FREQ_SENSITIVITY: select CPU_FREQ_TABLE Viresh Kumar
2013-06-12 14:23 ` Jacob Shin
2013-06-12 12:46 ` [PATCH 00/11] CPUFreq Kconfig fixes Arnd Bergmann
2013-06-12 14:28 ` Viresh Kumar
2013-06-12 14:49 ` Arnd Bergmann [this message]
2013-06-12 22:55 ` Rafael J. Wysocki
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=201306121649.41656.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
--cc=viresh.kumar@linaro.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