linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Russell Currey <ruscur@russell.cc>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/eeh: rename EEH from "extended" to "enhanced" error handling
Date: Wed, 17 Feb 2016 09:59:21 +1100	[thread overview]
Message-ID: <20160216225921.GA8768@gwshan> (raw)
In-Reply-To: <1455624365-4200-1-git-send-email-ruscur@russell.cc>

On Tue, Feb 16, 2016 at 11:06:05PM +1100, Russell Currey wrote:
>IBM online documentation for EEH uses "extended error handling" and
>"enhanced error handling" to refer to the same thing, in different
>places.  The only place mentioning it as "enhanced error handling" in the
>kernel is the MAINTAINERS file, and it's "extended" in some documentation.
>
>IBM originally defined EEH as "enhanced error handling", so standardise
>all mentions of EEH to use that term.
>
>Signed-off-by: Russell Currey <ruscur@russell.cc>

Acked-by: Gavin Shan <gwshan@linux.vnet.ibm.com>

Thanks,
Gavin

>---
>This is essentially a V2 (though it has the inverse result) of this patch:
>https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-February/139367.html
>---
> Documentation/powerpc/eeh-pci-error-recovery.txt | 2 +-
> arch/powerpc/kernel/eeh.c                        | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/Documentation/powerpc/eeh-pci-error-recovery.txt b/Documentation/powerpc/eeh-pci-error-recovery.txt
>index 9d4e33d..6781892 100644
>--- a/Documentation/powerpc/eeh-pci-error-recovery.txt
>+++ b/Documentation/powerpc/eeh-pci-error-recovery.txt
>@@ -12,7 +12,7 @@ Overview:
> The IBM POWER-based pSeries and iSeries computers include PCI bus
> controller chips that have extended capabilities for detecting and
> reporting a large variety of PCI bus error conditions.  These features
>-go under the name of "EEH", for "Extended Error Handling".  The EEH
>+go under the name of "EEH", for "Enhanced Error Handling".  The EEH
> hardware features allow PCI bus errors to be cleared and a PCI
> card to be "rebooted", without also having to reboot the operating
> system.
>diff --git a/arch/powerpc/kernel/eeh.c b/arch/powerpc/kernel/eeh.c
>index 40e4d4a..2e78466 100644
>--- a/arch/powerpc/kernel/eeh.c
>+++ b/arch/powerpc/kernel/eeh.c
>@@ -48,7 +48,7 @@
> 
> 
> /** Overview:
>- *  EEH, or "Extended Error Handling" is a PCI bridge technology for
>+ *  EEH, or "Enhanced Error Handling" is a PCI bridge technology for
>  *  dealing with PCI bus errors that can't be dealt with within the
>  *  usual PCI framework, except by check-stopping the CPU.  Systems
>  *  that are designed for high-availability/reliability cannot afford
>-- 
>2.7.1
>
>_______________________________________________
>Linuxppc-dev mailing list
>Linuxppc-dev@lists.ozlabs.org
>https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2016-02-16 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 12:06 [PATCH] powerpc/eeh: rename EEH from "extended" to "enhanced" error handling Russell Currey
2016-02-16 22:59 ` Gavin Shan [this message]
2016-04-11 12:35 ` Michael Ellerman

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=20160216225921.GA8768@gwshan \
    --to=gwshan@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ruscur@russell.cc \
    /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;
as well as URLs for NNTP newsgroup(s).