mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vitaly Wool" <vitalywool@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Mark Gross" <mgross@linux.intel.com>,
	"Preece Scott-PREECE" <scott.preece@motorola.com>,
	"pm list" <linux-pm@lists.osdl.org>,
	"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP]
Date: Tue, 12 Sep 2006 13:10:24 +0400	[thread overview]
Message-ID: <acd2a5930609120210w7ee5a156s5fa5bbc59aeabad8@mail.gmail.com> (raw)
In-Reply-To: <20060912083328.GA19197@elf.ucw.cz>

Pavel,

On 9/12/06, Pavel Machek <pavel@ucw.cz> wrote:
> Can we at least try adding that, before deciding cpufreq is unsuitable
> and starting new interface? I do not think issues are nearly as big as
> you think.. (at user<->kernel interface level, anyway; you'll need big
> changes under the hood).

who talks about user <-> kernel interface level changes at the moment?!

Vitaly

  reply	other threads:[~2006-09-12  9:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <450516E8.9010403@gmail.com>
     [not found] ` <20060911082025.GD1898@elf.ucw.cz>
     [not found]   ` <b0623b9bb79afacc77cddc6e39c96b62@nomadgs.com>
     [not found]     ` <20060911195546.GB11901@elf.ucw.cz>
     [not found]       ` <4505CCDA.8020501@gmail.com>
     [not found]         ` <20060911210026.GG11901@elf.ucw.cz>
     [not found]           ` <4505DDA6.8080603@gmail.com>
2006-09-11 22:56             ` Pavel Machek
2006-09-12  0:17               ` Mark Gross
2006-09-12  3:37                 ` Greg KH
2006-09-13 23:50                   ` [linux-pm] " David Singleton
2006-09-14  5:30                     ` Vitaly Wool
2006-09-14  5:55                     ` OpPoint summary Greg KH
2006-09-14  7:35                       ` [linux-pm] " Vitaly Wool
2006-09-14 16:55                       ` David Singleton
2006-09-14 17:03                       ` David Singleton
2006-09-14 17:07                       ` David Singleton
2006-09-14 17:25                         ` Auke Kok
2006-09-14 18:15                           ` [linux-pm] " Vitaly Wool
2006-09-14 18:17                           ` David Singleton
2006-09-17 17:48                         ` Pavel Machek
2006-09-18 14:33                           ` [linux-pm] " Richard A. Griffiths
2006-09-18 16:13                             ` Matthew Locke
2006-09-14 17:11                       ` David Singleton
2006-09-17  5:07                       ` David Singleton
2006-09-17 12:56                         ` Pavel Machek
2006-09-17 12:58                         ` Pavel Machek
2006-09-17 22:43                         ` [linux-pm] " Matthew Locke
2006-09-12  8:33                 ` cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP] Pavel Machek
2006-09-12  9:10                   ` Vitaly Wool [this message]
2006-09-12  9:16                     ` [linux-pm] " Pavel Machek
2006-09-12  9:23                       ` Vitaly Wool
2006-09-14 15:04                     ` Mark Gross
2006-09-14 14:58                   ` Mark Gross

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=acd2a5930609120210w7ee5a156s5fa5bbc59aeabad8@mail.gmail.com \
    --to=vitalywool@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mgross@linux.intel.com \
    --cc=pavel@ucw.cz \
    --cc=scott.preece@motorola.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®