cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH] Remove notify in speedstep_set_state [1/2]
Date: Fri, 11 Jun 2004 14:11:59 +0100	[thread overview]
Message-ID: <20040611131159.GE8779@redhat.com> (raw)
In-Reply-To: <20040611130745.GH1095@poupinou.org>

On Fri, Jun 11, 2004 at 03:07:45PM +0200, Bruno Ducrot wrote:
 > On Fri, Jun 11, 2004 at 01:18:22PM +0100, Dave Jones wrote:
 > > On Fri, Jun 11, 2004 at 12:02:23PM +0200, Bruno Ducrot wrote:
 > >  > Remove 'notify' in speedstep_set_state for speedstep-lib
 > >  > 
 > >  > Signed-off-by:  Bruno Ducrot <ducrot@poupinou.org>
 > > 
 > > How about [3/2] Fix speedstep-ich 8-)
 > 
 > It's expected to be done by the latest
 > speedstep_patch.2.6.7-rc3_SMT.diff from Christian Hoelbling ;)

Ah, I lost track of what happened with that one.
Dominik mentioned you found some bug in it, but I'm not sure
I saw any follow-up patch.  I'll go re-read the thread after
lunch and see if I can pick it up.

		Dave

  reply	other threads:[~2004-06-11 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 10:02 [PATCH] Remove notify in speedstep_set_state [1/2] Bruno Ducrot
2004-06-11 12:18 ` Dave Jones
2004-06-11 13:07   ` Bruno Ducrot
2004-06-11 13:11     ` Dave Jones [this message]
2004-06-11 13:24       ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08 17:15 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-08 15:30 ` Bruno Ducrot
2004-06-08 23:53   ` Christian Hoelbling
2004-06-09 15:47     ` Dominik Brodowski
2004-06-10  0:46       ` Christian Hoelbling
2004-06-10 15:37         ` Bruno Ducrot
2004-06-10 16:44           ` Dominik Brodowski
2004-06-10 19:26             ` [PATCH] Remove notify in speedstep_set_state [1/2] Bruno Ducrot

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=20040611131159.GE8779@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.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