linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ganesh <ganeshgr@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au
Cc: mahesh@linux.ibm.com, npiggin@gmail.com
Subject: Re: [PATCH v3 1/3] powerpc/pseries: Parse control memory access error
Date: Mon, 8 Nov 2021 14:11:55 +0530	[thread overview]
Message-ID: <a6ffe492-34a7-7e5e-f652-3fc302bfad20@linux.ibm.com> (raw)
In-Reply-To: <20210906084303.183921-1-ganeshgr@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 617 bytes --]

On 9/6/21 14:13, Ganesh Goudar wrote:

> Add support to parse and log control memory access
> error for pseries. These changes are made according to
> PAPR v2.11 10.3.2.2.12.
>
> Signed-off-by: Ganesh Goudar<ganeshgr@linux.ibm.com>
> ---
> v3: Modify the commit log to mention the document according
>      to which changes are made.
>      Define and use a macro to check if the effective address
>      is provided.
>
> v2: No changes.
> ---
>   arch/powerpc/platforms/pseries/ras.c | 36 ++++++++++++++++++++++++----
>   1 file changed, 32 insertions(+), 4 deletions(-)
>
Hi mpe, Any comments on this patch series?

[-- Attachment #2: Type: text/html, Size: 1023 bytes --]

      parent reply	other threads:[~2021-11-08  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  8:43 [PATCH v3 1/3] powerpc/pseries: Parse control memory access error Ganesh Goudar
2021-09-06  8:43 ` [PATCH v3 2/3] selftests/powerpc: Add test for real address error handling Ganesh Goudar
2021-09-06  8:43 ` [PATCH v3 3/3] powerpc/mce: Modify the real address error logging messages Ganesh Goudar
2021-11-08  8:41 ` Ganesh [this message]

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=a6ffe492-34a7-7e5e-f652-3fc302bfad20@linux.ibm.com \
    --to=ganeshgr@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    /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).