All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH 1/2] ondemand: updated tune for hardware coordination
Date: Tue, 01 Aug 2006 21:39:24 +0400	[thread overview]
Message-ID: <44CF91CC.3070003@linux.intel.com> (raw)
In-Reply-To: <20060801164315.GA9083@redhat.com>

Dave Jones wrote:
> On Tue, Aug 01, 2006 at 12:09:50PM +0400, Alexey Starikovskiy wrote:
>  > Dave Jones wrote:
>  > > On Mon, Jul 31, 2006 at 10:25:20PM +0400, Alexey Starikovskiy wrote:
>  > >  > 
>  > >  > cpufreq_ondemand.c |   13 ++++++++-----
>  > >  > 1 file changed, 8 insertions(+), 5 deletions(-)
>  > >  > 
>  > >  > Try to make dbs_check_cpu() call on all CPUs at the same jiffy.
>  > >  > This will help when multiple cores share P-states via Hardware Coordination.
>  > >  > 
>  > >  > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi at intel.com>
>  > >  > Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy at intel.com>
>  > > 
>  > > Still doesn't apply..
>  > > 
>  > > error: patch failed: drivers/cpufreq/cpufreq_ondemand.c:303
>  > > error: drivers/cpufreq/cpufreq_ondemand.c: patch does not apply
>  > It requires Arjan's patch to cpufreq, sitting in Linus tree for 3 days already.
> 
> This was after I'd rebased the cpufreq.git tree to Linus' latest yesterday.
> 
> 		Dave
> 
Just checked once again. Version I've sent yesterday cleanly applies to your
just updated cpufreq.git tree.

  reply	other threads:[~2006-08-01 17:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 18:25 [PATCH 1/2] ondemand: updated tune for hardware coordination Alexey Starikovskiy
2006-07-31 22:37 ` Dave Jones
2006-08-01  8:09   ` Alexey Starikovskiy
2006-08-01 16:43     ` Dave Jones
2006-08-01 17:39       ` Alexey Starikovskiy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-26 15:31 Alexey Starikovskiy

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=44CF91CC.3070003@linux.intel.com \
    --to=alexey_y_starikovskiy@linux.intel.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    /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.