From: "Németh Márton" <nm127@freemail.hu>
To: cpufreq@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] cpufreq: correct broken links and email address
Date: Fri, 10 Oct 2008 11:35:51 +0200 [thread overview]
Message-ID: <48EF21F7.1020308@freemail.hu> (raw)
From: Márton Németh <nm127@freemail.hu>
Replace the no longer working links and email address in the
documentation and in source code.
Signed-off-by: Márton Németh <nm127@freemail.hu>
---
diff -upr
linux-2.6.27-rc9.orig/arch/x86/kernel/cpu/cpufreq/p4-clockmod.c
linux-2.6.27-rc9.new/arch/x86/kernel/cpu/cpufreq/p4-clockmod.c
--- linux-2.6.27-rc9.orig/arch/x86/kernel/cpu/cpufreq/p4-clockmod.c
2008-10-08 17:11:44.000000000 +0200
+++ linux-2.6.27-rc9.new/arch/x86/kernel/cpu/cpufreq/p4-clockmod.c
2008-10-10 10:48:11.000000000 +0200
@@ -171,7 +171,7 @@ static unsigned int cpufreq_p4_get_frequ
}
if (c->x86 != 0xF) {
- printk(KERN_WARNING PFX "Unknown p4-clockmod-capable CPU.
Please send an e-mail to <cpufreq@lists.linux.org.uk>\n");
+ printk(KERN_WARNING PFX "Unknown p4-clockmod-capable CPU.
Please send an e-mail to <cpufreq@vger.kernel.org>\n");
return 0;
}
diff -upr
linux-2.6.27-rc9.orig/arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c
linux-2.6.27-rc9.new/arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c
---
linux-2.6.27-rc9.orig/arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c
2008-10-08 17:11:44.000000000 +0200
+++
linux-2.6.27-rc9.new/arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c
2008-10-10 10:48:39.000000000 +0200
@@ -26,7 +26,7 @@
#include <asm/cpufeature.h>
#define PFX "speedstep-centrino: "
-#define MAINTAINER "cpufreq@lists.linux.org.uk"
+#define MAINTAINER "cpufreq@vger.kernel.org"
#define dprintk(msg...) \
cpufreq_debug_printk(CPUFREQ_DEBUG_DRIVER, "speedstep-centrino", msg)
diff -upr linux-2.6.27-rc9.orig/Documentation/cpu-freq/index.txt
linux-2.6.27-rc9.new/Documentation/cpu-freq/index.txt
--- linux-2.6.27-rc9.orig/Documentation/cpu-freq/index.txt 2008-07-13
23:51:29.000000000 +0200
+++ linux-2.6.27-rc9.new/Documentation/cpu-freq/index.txt 2008-10-10
10:46:08.000000000 +0200
@@ -35,11 +35,9 @@ Mailing List
------------
There is a CPU frequency changing CVS commit and general list where
you can report bugs, problems or submit patches. To post a message,
-send an email to cpufreq@lists.linux.org.uk, to subscribe go to
-http://lists.linux.org.uk/mailman/listinfo/cpufreq. Previous post to the
-mailing list are available to subscribers at
-http://lists.linux.org.uk/mailman/private/cpufreq/.
-
+send an email to cpufreq@vger.kernel.org, to subscribe go to
+http://vger.kernel.org/vger-lists.html#cpufreq and follow the
+instructions there.
Links
-----
@@ -50,7 +48,7 @@ how to access the CVS repository:
* http://cvs.arm.linux.org.uk/
the CPUFreq Mailing list:
-* http://lists.linux.org.uk/mailman/listinfo/cpufreq
+* http://vger.kernel.org/vger-lists.html#cpufreq
Clock and voltage scaling for the SA-1100:
* http://www.lartmaker.nl/projects/scaling
next reply other threads:[~2008-10-09 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 9:35 Németh Márton [this message]
2008-10-09 12:59 ` [PATCH] cpufreq: correct broken links and email address Németh Márton
2008-10-09 13:22 ` Alan Cox
2008-10-09 17:50 ` Dave Jones
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=48EF21F7.1020308@freemail.hu \
--to=nm127@freemail.hu \
--cc=cpufreq@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox