From: Doug Thompson <norsk5@yahoo.com>
To: Jiri Kosina <trivial@kernel.org>, leemgs1@gmail.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
dougthompson@xmission.com, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Fix the meaning of EDAC abbreviation
Date: Wed, 3 Jun 2009 07:46:27 -0700 (PDT) [thread overview]
Message-ID: <255444.45685.qm@web50108.mail.re2.yahoo.com> (raw)
--- On Tue, 6/2/09, GeunSik Lim <leemgs1@gmail.com> wrote:
> From: GeunSik Lim <leemgs1@gmail.com>
> Subject: [PATCH] Fix the meaning of EDAC abbreviation
> To: "Jiri Kosina" <trivial@kernel.org>
> Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, dougthompson@xmission.com
> Date: Tuesday, June 2, 2009, 6:04 PM
>
>
> Dear Jiri Kosina,
>
> This is trivial patch about meaning of EDAC in the
> driver/edac/Kconfig file.
> * Screenshot after patch :
> http://blogfiles16.naver.net/data42/2009/6/3/31/edac-before-after-invain.png
>
>
> Thanks,
>
>
> Subject: [PATCH] Fix the meaning of EDAC abbreviation
>
> Fix the meaning of EDAC(Error Detection And Correction)
> correctly.
> - http://bluesmoke.sourceforge.net
>
> Signed-off-by: GeunSik Lim
> <geunsik.lim@samsung.com>
> ---
> drivers/edac/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/edac/Kconfig b/drivers/edac/Kconfig
> index 956982f..2a81915 100644
> --- a/drivers/edac/Kconfig
> +++ b/drivers/edac/Kconfig
> @@ -5,7 +5,7 @@
> #
>
> menuconfig EDAC
> - bool "EDAC - error detection and
> reporting"
> + bool "EDAC - Error Detection And
> Correction"
> depends on HAS_IOMEM
> depends on X86 || PPC
> help
> --
> 1.6.3.1
Good catch. All these years and I didn't see it. Always need more eyes
Acked-by: Doug Thompson <dougthompson@xmission.com>
next reply other threads:[~2009-06-03 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 14:46 Doug Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-03 14:51 Doug Thompson
2009-06-03 0:04 GeunSik Lim
2009-06-03 7:42 ` Alan Cox
2009-06-03 8:34 ` GeunSik Lim
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=255444.45685.qm@web50108.mail.re2.yahoo.com \
--to=norsk5@yahoo.com \
--cc=akpm@osdl.org \
--cc=dougthompson@xmission.com \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
Powered by JetHome