From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cpufreq deprecation
Date: Tue, 17 Aug 2004 15:12:04 -0700 [thread overview]
Message-ID: <20040817151204.28ecb1a0.akpm@osdl.org> (raw)
In-Reply-To: <20040817105859.GA1497@elf.ucw.cz>
Pavel Machek <pavel@ucw.cz> wrote:
>
> Today I learned that /proc/cpufreq is going to be removed
> from 2.6.. I thought that 2.6 means "no interface changes" :-(.
Well, we'll see. One very good reason for adding such a runtime warning is
to give people six months to convince the developers that it's a bad idea.
> Anyway, if
> we are going to warn about it, we might want to include newline...
Sure.
> - printk(KERN_INFO "Access to /proc/sys/cpu/ is deprecated and will be removed from (new) 2.6. kernels soon after 2005-01-01");
> + printk(KERN_INFO "Access to /proc/sys/cpu/ is deprecated and will be removed from (new) 2.6. kernels soon after 2005-01-01\n");
hrmpf. The original author is hereby impaled upon a metaphorical 80-col
xterm. Shall fix that too.
prev parent reply other threads:[~2004-08-17 22:08 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
2004-08-17 22:12 ` Andrew Morton [this message]
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=20040817151204.28ecb1a0.akpm@osdl.org \
--to=akpm@osdl.org \
--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