From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@zip.com.au>,
kernel list <linux-kernel@vger.kernel.org>
Subject: cpufreq deprecation
Date: Tue, 17 Aug 2004 12:58:59 +0200 [thread overview]
Message-ID: <20040817105859.GA1497@elf.ucw.cz> (raw)
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
--- clean-mm/drivers/cpufreq/cpufreq_userspace.c 2004-08-17 12:21:43.000000000 +0200
+++ linux-mm/drivers/cpufreq/cpufreq_userspace.c 2004-08-17 12:55:04.000000000 +0200
@@ -174,7 +174,7 @@
if (!warning_print) {
warning_print++;
- 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");
}
if (write) {
@@ -214,7 +214,7 @@
if (!warning_print) {
warning_print++;
- 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");
}
if (oldval && oldlenp) {
--- clean-mm/drivers/cpufreq/proc_intf.c 2004-08-17 12:21:43.000000000 +0200
+++ linux-mm/drivers/cpufreq/proc_intf.c 2004-08-17 12:54:53.000000000 +0200
@@ -115,7 +115,7 @@
if (!warning_print) {
warning_print++;
- printk(KERN_INFO "Access to /proc/cpufreq is deprecated and will be removed from (new) 2.6. kernels soon after 2005-01-01");
+ printk(KERN_INFO "Access to /proc/cpufreq is deprecated and will be removed from (new) 2.6. kernels soon after 2005-01-01\n");
}
p += sprintf(p, " minimum CPU frequency - maximum CPU frequency - policy\n");
@@ -190,7 +190,7 @@
if (!warning_print) {
warning_print++;
- printk(KERN_INFO "Access to /proc/cpufreq is deprecated and will be removed from (new) 2.6. kernels soon after 2005-01-01");
+ printk(KERN_INFO "Access to /proc/cpufreq is deprecated and will be removed from (new) 2.6. kernels soon after 2005-01-01\n");
}
proc_string[count] = '\0';
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next reply other threads:[~2004-08-17 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 10:58 Pavel Machek [this message]
2004-08-17 14:39 ` cpufreq deprecation Ray Bryant
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=20040817105859.GA1497@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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.