cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@osdl.org>,
	Bruno Ducrot <ducrot@poupinou.org>,
	mark.langsdorf@amd.com,
	Cpufreq mailing list <cpufreq@www.linux.org.uk>,
	paul.devriendt@amd.com
Subject: Re: powernow-k8: support acpi
Date: Tue, 6 Apr 2004 16:47:50 +0100	[thread overview]
Message-ID: <20040406154750.GE6930@redhat.com> (raw)
In-Reply-To: <20040406145502.GA7307@dominikbrodowski.de>

On Tue, Apr 06, 2004 at 04:55:02PM +0200, Dominik Brodowski wrote:

 > Just found a small bug which would leave the preempt count negative(!) in
 > special cases. Patch is attached.

good catch. applied.

 > > You can grab what I have in my tree pending pushing to Linus at
 > > http://www.codemonkey.org.uk/projects/cpufreq/pending.diff
 > 
 > Will http://www.codemonkey.org.uk/projects/bitkeeper/cpufreq/
 > be a permanent institution, or is it just available for the moment?

I set it up this morning to do a snapshot each night along with the
other trees one level up from there.  It'll continually keep one weeks
worth of patches.

 > > <f> found a funny bug in the powernow-k8 acpi changes
 > > <f> when  acpi is disabled processor.ko won't load, but the new module needs symbols from that
 > > <f> i added a hack to keep it loaded anyways
 > > 
 > > Be nice to get that fixed, and merged before these changes get pushed to mainline.
 > 
 > Hm. Keeping processor.ko loaded seems to be an ugly hack to me. However, I
 > can't see a way (yet) how powernow-k8.ko can rely on processor.ko's objects
 > but not depend on it if these are not neeeded (psb case).

True, it's a sledgehammer to crack a walnut, but I'm not sure messing with
weak symbols would be any cleaner, and other than that or moving bits out
to a seperate module (double ugh), I don't really have any ideas.

		Dave

  reply	other threads:[~2004-04-06 15:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <99F2150714F93F448942F9A9F112634C1163C8D7@txexmtae.amd.com>
     [not found] ` <20040321185417.GA7969@dominikbrodowski.de>
2004-03-26 12:29   ` powernow-k8: support acpi Pavel Machek
2004-04-01 23:56     ` Dave Jones
2004-04-02  8:30       ` Pavel Machek
2004-04-02  9:02         ` Dave Jones
2004-04-02 11:13         ` Dave Jones
2004-04-02 16:24       ` Bruno Ducrot
2004-04-02 16:39         ` Dave Jones
2004-04-02 17:09           ` Pavel Machek
2004-04-06 13:07             ` Dave Jones
2004-04-06 14:55               ` Dominik Brodowski
2004-04-06 15:47                 ` Dave Jones [this message]
2004-04-06 16:55                   ` Dominik Brodowski
2004-04-06 17:05                     ` Dave Jones
2004-04-06 21:57                       ` Dominik Brodowski
2004-04-08 13:11               ` Pavel Machek
2004-04-02 16:39         ` Dominik Brodowski
2004-04-02 16:46           ` Dominik Brodowski
2004-04-02 16:59 paul.devriendt
2004-04-02 18:40 ` 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=20040406154750.GE6930@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=mark.langsdorf@amd.com \
    --cc=paul.devriendt@amd.com \
    --cc=pavel@ucw.cz \
    /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