public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Amit Kucheria <amit.kucheria@linaro.org>,
	Borislav Petkov <bp@alien8.de>,
	Steve Bannister <Steve.Bannister@arm.com>,
	Lists linaro-dev <linaro-dev@lists.linaro.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	cpufreq@vger.kernel.org,
	Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
Subject: Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
Date: Wed, 06 Feb 2013 11:38:40 +0100	[thread overview]
Message-ID: <1713890.Dj4ufUrfMM@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpo=T+YJxkxyWJQ_SdsFHcY_Xv-SXy_mZNLe7a3CtDF-7gw@mail.gmail.com>

On Wednesday, February 06, 2013 03:45:58 PM Viresh Kumar wrote:
> On 6 February 2013 15:38, Amit Kucheria <amit.kucheria@linaro.org> wrote:
> > On Wed, Feb 6, 2013 at 3:28 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >> I have pushed the complete patchset here:
> >>
> >> http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/cpufreq-updates
> >>
> >
> > Viresh, perhaps you should ask Stephen Rothwell to pull in your tree
> > to get some more testing before Rafael pulls it in for 3.10?
> 
> Its has been made clear by Rafael that these patches wouldn't make it for
> 3.9 (though i wanted them to :) ), and so once the merge window is over
> Rafael might pull them in and so they would reach Stephen's linux-next too...
> 
> I am not sure if sending a cpufreq pull request directly to Stephen is
> preferred.
> @Rafael: ??

You may do that, if you want, but that's slightly confusing.

Also the policy is that material which is not going to be included into v3.9
shouldn't be in linux-next before v3.9-rc1.

Moreover, for build testing it is sufficient to put it into a branch somewhere
at git.kernel.org (as you have already noticed :-)).

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-02-06 10:38 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 11:38 [PATCH 0/4] CPUFreq: Implement per policy instances of governors Viresh Kumar
     [not found] ` <cover.1359976493.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-04 11:38   ` [PATCH 1/4] cpufreq: Don't check cpu_online(policy->cpu) Viresh Kumar
2013-02-04 11:38   ` [PATCH 2/4] cpufreq: stats: Get rid of CPUFREQ_STATDEVICE_ATTR Viresh Kumar
2013-02-04 11:38   ` [PATCH 3/4] cpufreq: Add per policy governor-init/exit infrastructure Viresh Kumar
2013-02-04 11:38   ` [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors Viresh Kumar
2013-02-10 21:14     ` Francesco Lavra
2013-02-11  4:16       ` Viresh Kumar
2013-02-11  4:39         ` Viresh Kumar
2013-02-04 12:17   ` [PATCH 0/4] CPUFreq: " Rafael J. Wysocki
2013-02-04 12:24     ` Viresh Kumar
2013-02-04 12:32       ` Borislav Petkov
2013-02-04 12:54         ` Viresh Kumar
2013-02-04 13:04           ` Borislav Petkov
2013-02-04 13:25             ` Viresh Kumar
2013-02-04 13:36               ` Borislav Petkov
2013-02-04 13:58                 ` Viresh Kumar
2013-02-04 14:09                   ` Borislav Petkov
2013-02-04 14:21                     ` Viresh Kumar
2013-02-04 15:05                       ` Borislav Petkov
2013-02-04 15:37                         ` Viresh Kumar
2013-02-04 16:50                           ` Borislav Petkov
2013-02-05  7:20                             ` Viresh Kumar
2013-02-05  9:15                               ` Borislav Petkov
     [not found]                                 ` <20130205091532.GA4827-fF5Pk5pvG8Y@public.gmane.org>
2013-02-05  9:47                                   ` Viresh Kumar
2013-02-05 10:27                                     ` Borislav Petkov
2013-02-05 10:43                                       ` Viresh Kumar
2013-02-05 11:04                                         ` Borislav Petkov
2013-02-05 11:12                                           ` Viresh Kumar
2013-02-05 11:19                                             ` Borislav Petkov
2013-02-05 11:26                                               ` Viresh Kumar
2013-02-05 11:32                                                 ` Borislav Petkov
2013-02-05 12:24                                                   ` Viresh Kumar
2013-02-05 13:22                                                     ` Borislav Petkov
2013-02-05 13:55                                                       ` Viresh Kumar
2013-02-05  9:36                 ` Viresh Kumar
     [not found]                   ` <CAKohpokejWugM+wP5xcqp0F9AggLxuEf9Ox5fDViMxJh1c+kEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 11:29                     ` Charles Garcia-Tobin
2013-02-05 11:39                       ` Borislav Petkov
2013-02-05 18:38                         ` Charles Garcia-Tobin
2013-02-05 18:44                           ` Borislav Petkov
2013-02-05 16:21 ` Viresh Kumar
2013-02-06  9:58   ` Viresh Kumar
2013-02-06 10:08     ` Amit Kucheria
2013-02-06 10:15       ` Viresh Kumar
2013-02-06 10:38         ` Rafael J. Wysocki [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=1713890.Dj4ufUrfMM@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=Charles.Garcia-Tobin@arm.com \
    --cc=Steve.Bannister@arm.com \
    --cc=amit.kucheria@linaro.org \
    --cc=bp@alien8.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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