All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@redhat.com>, Ray Bryant <raybry@sgi.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: cpufreq deprecation
Date: Tue, 17 Aug 2004 21:54:10 +0200	[thread overview]
Message-ID: <20040817195410.GI19009@elf.ucw.cz> (raw)
In-Reply-To: <20040817164509.GB19243@redhat.com>

Hi!

>  > A scan of the lkml archives on theaimsgroup for cpufreq shows only this 
>  > message about deprecation.  Where was this discussed?
> 
> Probably cpufreq list around the time cpufreq was first merged to mainline 2.6.
> 
> I never wanted to really see the proc stuff hit 2.6 at all, but
> someone (maybe Dominik) suggested that as there were tools using it,
> (a multitude of cpu scaling daemons appeared), we should drag it into 2.6
> too, at least until the daemons caught up with the preferred
> interface.

I do not think changing interface in half of stable series is good
idea, but yes, it was market deprecated since day one. Keeping at
least read-only /proc/cpufreq would be nice. Or perhaps merging that
info into /proc/cpuinfo?
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2004-08-17 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 10:58 cpufreq deprecation Pavel Machek
2004-08-17 14:39 ` Ray Bryant
2004-08-17 16:45   ` Dave Jones
2004-08-17 19:54     ` Pavel Machek [this message]
2004-08-17 22:12 ` Andrew Morton

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=20040817195410.GI19009@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raybry@sgi.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 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.