mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH] cpufreq: cpufreq-cpu0: use the exact frequency for clk_set_rate()
Date: Wed, 05 Jun 2013 14:15:28 +0200	[thread overview]
Message-ID: <91385266.39H0Z0D5Kr@vostro.rjw.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.1306051323160.19739@axis700.grange>

On Wednesday, June 05, 2013 01:25:37 PM Guennadi Liakhovetski wrote:
> Hi Rafael
> 
> On Wed, 22 May 2013, Rafael J. Wysocki wrote:
> 
> > On Wednesday, May 22, 2013 08:12:22 PM Guennadi Liakhovetski wrote:
> > > Hi Rafael
> > > 
> > > I don't see this patch in your cpufreq branch nor in next or Linus' trees, 
> > > has it been pulled yet?
> > 
> > No, I haven't applied it yet, not sure why exactly.
> > 
> > In the future it's better to CC cpufreq patches to linux-pm@vger.kernel.org so
> > that the kernel.org Patchwork can pick them up.  I'm much less likely to
> > overlook them then.
> > 
> > This is a fix, so do we need it in 3.10-rc?
> 
> Would be good, yes.

OK, queued up for 3.10.

Thanks,
Rafael


> > > On Thu, 28 Mar 2013, Shawn Guo wrote:
> > > 
> > > > On Wed, Mar 27, 2013 at 11:46:38PM +0100, Guennadi Liakhovetski wrote:
> > > > > Hi Shawn
> > > > > 
> > > > > On Mon, 25 Feb 2013, Guennadi Liakhovetski wrote:
> > > > > 
> > > > > > clk_set_rate() isn't supposed to accept approximate frequencies, instead
> > > > > > a supported frequency should be obtained from clk_round_rate() and then
> > > > > > used to set the clock.
> > > > > > 
> > > > > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > > > > 
> > > > > Can I have your ack for this one, please?
> > > > 
> > > > Acked-by: Shawn Guo <shawn.guo@linaro.org>
> 
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-06-05 12:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 17:22 Guennadi Liakhovetski
2013-03-27 22:46 ` Guennadi Liakhovetski
2013-03-28  2:07   ` Shawn Guo
2013-05-22 18:12     ` Guennadi Liakhovetski
2013-05-22 19:31       ` Rafael J. Wysocki
2013-06-05 11:25         ` Guennadi Liakhovetski
2013-06-05 12:15           ` Rafael J. Wysocki [this message]
2013-03-28  7:11 ` 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=91385266.39H0Z0D5Kr@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.guo@linaro.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

all inboxes | Powered by JetHome®