Re: [PATCH] Fix the meaning of EDAC abbreviation

[Doug Thompson]

--- On Wed, 6/3/09, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:

> From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
> Subject: Re: [PATCH] Fix the meaning of EDAC abbreviation
> To: leemgs1@xxxxxxxxx
> Cc: "Jiri Kosina" <trivial@xxxxxxxxxx>, "linux-kernel" <linux-kernel@xxxxxxxxxxxxxxx>, dougthompson@xxxxxxxxxxxx
> Date: Wednesday, June 3, 2009, 1:42 AM
> > Fix the meaning of EDAC(Error
> Detection And Correction) correctly.
> >  - http://bluesmoke.sourceforge.net
> > 
> >         Signed-off-by:
> GeunSik Lim <geunsik.lim@xxxxxxxxxxx>
> > ---
> >  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"
> 
> The code started off as one thing and acquired its name but
> a primary
> function of it now is indeed reporting rather than just
> correction. The
> name has stuck but the functionality doesn't quite match -
> so the
> existing menuconfig entry is actually more helpful.
> 

Alan has been "connected" with "bluesmoke"/EDAC far longer than I have and probably a better overall history of it.

Yet the EDAC modules harvest the events generated by the Error Detection and Correction hardware and present it, via reporting and he points out. But in spite of just being the "reporters", the modules manage the "detectors" in a way and deal with most of the "EDAC" system

I like the new patch mod

doug t

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/