From: Bruno Ducrot <ducrot@poupinou.org>
To: omv <omv@danhartman.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: 2.4 patch and powernow-k8
Date: Mon, 13 Dec 2004 14:32:24 +0100 [thread overview]
Message-ID: <20041213133224.GA2140@poupinou.org> (raw)
In-Reply-To: <41B0D199.9000309@danhartman.org>
On Fri, Dec 03, 2004 at 12:50:33PM -0800, omv wrote:
> My version (from CVS on sunday, i think) looked a bit different - the
> first block didn't have the __devexit at all, and the second was static
> int __exit drc_cpu_exit. I modified the second block to remove the _exit.
It's a bit old. I have to backport the acpilib stuff first.
>
> That appeared to do the trick - built fine. It now looks like
>
> static int drv_cpu_exit (struct cpufreq_policy *pol)
Commited. Thanks.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-12-13 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:13 2.4 patch and powernow-k8 omv
2004-12-03 9:09 ` Dominik Brodowski
2004-12-03 20:50 ` omv
2004-12-13 13:32 ` Bruno Ducrot [this message]
2004-12-13 18:59 ` omv
2004-12-14 12:00 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2004-12-03 0:00 Langsdorf, Mark
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=20041213133224.GA2140@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=omv@danhartman.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 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.