From: Ray Bryant <raybry@sgi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: cpufreq deprecation
Date: Tue, 17 Aug 2004 09:39:12 -0500 [thread overview]
Message-ID: <41221890.8070307@sgi.com> (raw)
In-Reply-To: <20040817105859.GA1497@elf.ucw.cz>
Pavel,
A scan of the lkml archives on theaimsgroup for cpufreq shows only this
message about deprecation. Where was this discussed? Is there an alternative
for this information being proposed?
Thanks,
Ray
Pavel Machek wrote:
> Hi!
>
> Today I learned that /proc/cpufreq is going to be removed from
> 2.6.. I thought that 2.6 means "no interface changes" :-(. Anyway, if
> we are going to warn about it, we might want to include newline...
>
> Please apply,
> Pavel
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
next prev parent reply other threads:[~2004-08-17 14:36 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 [this message]
2004-08-17 16:45 ` Dave Jones
2004-08-17 19:54 ` Pavel Machek
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=41221890.8070307@sgi.com \
--to=raybry@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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