From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: PATCH: Bluesmoke missing renames
Date: Fri, 21 Oct 2005 14:37:23 +0100 [thread overview]
Message-ID: <1129901843.26367.46.camel@localhost.localdomain> (raw)
As was noted on and off list a couple of places still had old naming
Signed-off-by: Alan Cox <alan@redhat.com>
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.14-rc4-mm1/drivers/edac/Kconfig linux-2.6.14-rc4-mm1/drivers/edac/Kconfig
--- linux.vanilla-2.6.14-rc4-mm1/drivers/edac/Kconfig 2005-10-20 16:12:39.000000000 +0100
+++ linux-2.6.14-rc4-mm1/drivers/edac/Kconfig 2005-10-20 17:05:58.000000000 +0100
@@ -34,9 +34,9 @@
depends on EDAC
help
Some systems are able to detect and correct errors in main
- memory. Bluesmoke can report statistics on memory error
+ memory. EDAC can report statistics on memory error
detection and correction (EDAC - or commonly referred to ECC
- errors). Bluesmoke will also try to decode where these errors
+ errors). EDAC will also try to decode where these errors
occurred so that a particular failing memory module can be
replaced. If unsure, select 'Y'.
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.14-rc4-mm1/drivers/edac/e752x_edac.c linux-2.6.14-rc4-mm1/drivers/edac/e752x_edac.c
--- linux.vanilla-2.6.14-rc4-mm1/drivers/edac/e752x_edac.c 2005-10-20 16:12:39.000000000 +0100
+++ linux-2.6.14-rc4-mm1/drivers/edac/e752x_edac.c 2005-10-20 17:06:17.000000000 +0100
@@ -13,7 +13,7 @@
* Wang Zhenyu at intel.com
* Dave Jiang at mvista.com
*
- * $Id: bluesmoke_e752x.c,v 1.5.2.11 2005/10/05 00:43:44 dsp_llnl Exp $
+ * $Id: edac_e752x.c,v 1.5.2.11 2005/10/05 00:43:44 dsp_llnl Exp $
*
*/
next reply other threads:[~2005-10-21 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 13:37 Alan Cox [this message]
2005-10-21 13:13 ` Jesper Juhl
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=1129901843.26367.46.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.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
all inboxes | Powered by JetHome®