From: Ducrot Bruno <ducrot@poupinou.org>
To: Dominik Brodowski <linux@brodo.de>
Cc: Hiroshi Miura <miura@da-cha.org>,
"'cpufreq@www linux org uk'" <cpufreq@www.linux.org.uk>
Subject: Re: speedstep-smi into -ac ?
Date: Mon, 8 Sep 2003 14:30:25 +0200 [thread overview]
Message-ID: <20030908123025.GL408@poupinou.org> (raw)
In-Reply-To: <20030908092317.GB1258@brodo.de>
On Mon, Sep 08, 2003 at 11:23:17AM +0200, Dominik Brodowski wrote:
> On Mon, Sep 08, 2003 at 10:32:55AM +0200, Ducrot Bruno wrote:
> > On Sun, Sep 07, 2003 at 08:55:03PM +0200, Dominik Brodowski wrote:
> > > On Fri, Sep 05, 2003 at 10:46:45AM +0200, Ducrot Bruno wrote:
> > > > Warn: I have not implemented the .resume callback. It need to
> > > > be done correctly in core at first, and it seems to be not so
> > > > well designed at first read (at core, not in the driver).
> > >
> > > Why?
> > >
> >
> > There is no restore like stuff in 2.4 backport, nor in ac (or
> > I'm blind).
>
> Actually, I meant "why do you consider the ->resume implementation to be 'not
> so well designed'"?
I'm talking about 2.4, not 2.6. If I want to make the ->resume stuff
in 2.4, there is a need to make something like
drivers/cpufreq/cpufreq::cpufreq_resume
in 2.4 backport at first.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2003-09-08 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 14:52 [new] event mode on speedstep-smi Hiroshi Miura
2003-09-04 15:30 ` Ducrot Bruno
2003-09-04 23:40 ` Hiroshi Miura
2003-09-05 6:56 ` Dominik Brodowski
2003-09-05 13:07 ` Ducrot Bruno
2003-09-04 23:25 ` Dominik Brodowski
2003-09-04 23:53 ` Hiroshi Miura
2003-09-05 6:54 ` speedstep-smi into -ac ? Dominik Brodowski
2003-09-05 8:46 ` Ducrot Bruno
2003-09-07 18:55 ` Dominik Brodowski
2003-09-08 8:32 ` Ducrot Bruno
2003-09-08 9:23 ` Dominik Brodowski
2003-09-08 12:30 ` Ducrot Bruno [this message]
2003-09-05 14:51 ` [new] event mode on speedstep-smi Ducrot Bruno
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=20030908123025.GL408@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@brodo.de \
--cc=miura@da-cha.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.