From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Patch Tracking <patches@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13
Date: Wed, 14 Aug 2013 07:56:44 +0530 [thread overview]
Message-ID: <CAKohpokOmv+CcL61dzkMgTNxY5rKb4A863CUAX_Jav4KyHF3DA@mail.gmail.com> (raw)
In-Reply-To: <1437762.edDpfxPldn@vostro.rjw.lan>
On 14 August 2013 01:31, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday, August 13, 2013 07:01:04 PM Viresh Kumar wrote:
> Are the three patches in this series prerequisite for the big target_index
> one? If so, I think they can go into 3.12 actually, if they are ACKed by the
> appropriate platform maintainers.
Yes, but they depend on cpufreq_table_validate_and_show() which
will also go in 3.13 and so these will be made part of that series in
future..
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13
Date: Wed, 14 Aug 2013 07:56:44 +0530 [thread overview]
Message-ID: <CAKohpokOmv+CcL61dzkMgTNxY5rKb4A863CUAX_Jav4KyHF3DA@mail.gmail.com> (raw)
In-Reply-To: <1437762.edDpfxPldn@vostro.rjw.lan>
On 14 August 2013 01:31, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday, August 13, 2013 07:01:04 PM Viresh Kumar wrote:
> Are the three patches in this series prerequisite for the big target_index
> one? If so, I think they can go into 3.12 actually, if they are ACKed by the
> appropriate platform maintainers.
Yes, but they depend on cpufreq_table_validate_and_show() which
will also go in 3.13 and so these will be made part of that series in
future..
next prev parent reply other threads:[~2013-08-14 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:31 [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13 Viresh Kumar
2013-08-13 13:31 ` Viresh Kumar
2013-08-13 13:31 ` [PATCH 1/3] cpufreq: sa11x0: Expose frequency table Viresh Kumar
2013-08-13 13:31 ` Viresh Kumar
2013-08-13 13:31 ` [PATCH 2/3] cpufreq: sa11x0: let cpufreq core initialize struct policy fields Viresh Kumar
2013-08-13 13:31 ` Viresh Kumar
2013-08-13 13:31 ` [PATCH 3/3] cpufreq: sa11x0: Use generic cpufreq routines Viresh Kumar
2013-08-13 13:31 ` Viresh Kumar
2013-08-13 20:01 ` [PATCH 0/3] cpufreq: sa11x0: cleanups for 3.13 Rafael J. Wysocki
2013-08-13 20:01 ` Rafael J. Wysocki
2013-08-14 2:26 ` Viresh Kumar [this message]
2013-08-14 2:26 ` Viresh Kumar
2013-08-14 2:26 ` Viresh Kumar
2013-08-14 13:14 ` Rafael J. Wysocki
2013-08-14 13:14 ` Rafael J. Wysocki
2013-08-14 13:14 ` 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=CAKohpokOmv+CcL61dzkMgTNxY5rKb4A863CUAX_Jav4KyHF3DA@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
/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.