From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
patches@linaro.org, arvind.chauhan@arm.com,
robin.randhawa@arm.com, Steve.Bannister@arm.com,
Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com,
jacob.shin@amd.com
Subject: Re: [PATCH V4 0/2] Implement per policy instance of governor
Date: Sun, 31 Mar 2013 03:49:13 +0200 [thread overview]
Message-ID: <4183493.GBcPoVddxx@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohponaAyo2BL3X+rxNTO9-u88dfj7Vho6zRyUmvct6XyHyVw@mail.gmail.com>
On Sunday, March 31, 2013 07:00:16 AM Viresh Kumar wrote:
> On 31 March 2013 03:38, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > OK, I'll remove it.
>
> Thanks.
>
> > And by the way, I'm no longer amused with the mess going on in the cpufreq land.
> >
> > Please send me *patches*. I'm not interested in git pointers.
>
> Hmm.
>
> > Moreover, please send those patches in a way allowing me to figure out the
> > ordering without looking into your git tree.
>
> Yes, i was planning to do so.
>
> > If you have a number of outstanding cpufreq patches for me to apply, please
> > create a patch series out of them and send it.
>
> Do you mean, i should merge all stuff i have queued up for 3.10 in a
> single patchset?
> Like for-3.10? Will do.
Yes, thanks.
But the patches moving cpufreq drivers into drivers/cpufreq from somewhere else
need each an ACK from the maintainer of that other place. I won't take any
patches like that without AKCs.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-03-31 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:58 Viresh Kumar
2013-03-27 15:58 ` [PATCH V4 1/2] cpufreq: Add per policy governor-init/exit infrastructure Viresh Kumar
2013-03-27 15:58 ` [PATCH V4 2/2] cpufreq: governor: Implement per policy instances of governors Viresh Kumar
2013-03-27 17:19 ` [PATCH V4 0/2] Implement per policy instance of governor Jacob Shin
2013-03-30 2:17 ` Rafael J. Wysocki
2013-03-30 3:36 ` Viresh Kumar
2013-03-30 22:08 ` Rafael J. Wysocki
2013-03-31 1:30 ` Viresh Kumar
2013-03-31 1:49 ` Rafael J. Wysocki [this message]
2013-03-31 3:47 ` Viresh Kumar
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=4183493.GBcPoVddxx@vostro.rjw.lan \
--to=rjw@sisk.pl \
--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=jacob.shin@amd.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--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
all inboxes | Powered by JetHome®