public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: [PATCH] Bluesmoke is now EDAC
Date: Mon, 17 Oct 2005 15:13:16 +0200	[thread overview]
Message-ID: <200510171513.16597.jesper.juhl@gmail.com> (raw)

I believe this sub-system was deliberately renamed from Bluesmoke to EDAC. In
that case, we should probably get rid of the remaining Bluesmoke references
and change them into EDAC.

This patch changes Bluesmoke into EDAC in Kconfig and Makefile and I also took
the liberty of rewriting some of the help text slightly.


Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---

 drivers/edac/Kconfig  |   19 +++++++++----------
 drivers/edac/Makefile |    2 +-
 2 files changed, 10 insertions(+), 11 deletions(-)

--- linux-2.6.14-rc4-mm1-orig/drivers/edac/Kconfig	2005-10-17 15:08:56.000000000 +0200
+++ linux-2.6.14-rc4-mm1/drivers/edac/Kconfig	2005-10-17 15:08:16.000000000 +0200
@@ -15,8 +15,8 @@
 	  EDAC is designed to report errors in the core system.
 	  These are low-level errors that are reported in the CPU or
 	  supporting chipset: memory errors, cache errors, PCI errors,
-	  thermal throttling, etc..  If unsure, select 'Y'.
-
+	  thermal throttling, etc.
+	  If unsure, select 'Y'.
 
 comment "Reporting subsystems"
 	depends on EDAC
@@ -26,8 +26,8 @@
 	depends on EDAC
 	help
 	  This turns on debugging information for the entire EDAC
-	  sub-system. You can insert module with "debug_level=x", current
-	  there're four debug levels (x=0,1,2,3 from low to high).
+	  sub-system. You can insert module with "debug_level=x", currently
+	  there are four debug levels (x=0,1,2,3 from low to high).
 	  Usually you should select 'N'.
 
 config EDAC_MM_EDAC
@@ -35,12 +35,11 @@
 	depends on EDAC
 	help
 	  Some systems are able to detect and correct errors in main
-	  memory.  Bluesmoke 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
-	  occurred so that a particular failing memory module can be
-	  replaced.  If unsure, select 'Y'.
-
+	  memory.  EDAC can report statistics on memory error detection
+	  and correction (commonly referred to ECC 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'.
 
 config EDAC_AMD76X
 	tristate "AMD 76x (760, 762, 768)"
--- linux-2.6.14-rc4-mm1-orig/drivers/edac/Makefile	2005-10-17 12:00:36.000000000 +0200
+++ linux-2.6.14-rc4-mm1/drivers/edac/Makefile	2005-10-17 15:03:49.000000000 +0200
@@ -1,5 +1,5 @@
 #
-# Makefile for the Linux kernel bluesmoke drivers.
+# Makefile for the Linux kernel EDAC drivers.
 #
 # Copyright 02 Jul 2003, Linux Networx (http://lnxi.com)
 # This file may be distributed under the terms of the




             reply	other threads:[~2005-10-17 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 13:13 Jesper Juhl [this message]
2005-10-17 20:23 ` [PATCH] Bluesmoke is now EDAC Alan Cox

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=200510171513.16597.jesper.juhl@gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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