From: Michael Ellerman <mpe@ellerman.id.au>
To: Ganesh <ganeshgr@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: mahesh@linux.ibm.com, npiggin@gmail.com
Subject: Re: [PATCH] powerpc/pseries/mce: Fix a typo in error type assignment
Date: Mon, 19 Apr 2021 22:39:54 +1000 [thread overview]
Message-ID: <87y2decusl.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <4c45d421-ea8c-6243-ee15-ebc85dc733a6@linux.ibm.com>
Ganesh <ganeshgr@linux.ibm.com> writes:
> On 4/17/21 6:06 PM, Michael Ellerman wrote:
>
>> Ganesh Goudar <ganeshgr@linux.ibm.com> writes:
>>> The error type is ICACHE and DCACHE, for case MCE_ERROR_TYPE_ICACHE.
>> Do you mean "is ICACHE not DCACHE" ?
>
> Right :), Should I send v2 ?
No I can fix it up :)
cheers
>>> Signed-off-by: Ganesh Goudar <ganeshgr@linux.ibm.com>
>>> ---
>>> arch/powerpc/platforms/pseries/ras.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/powerpc/platforms/pseries/ras.c b/arch/powerpc/platforms/pseries/ras.c
>>> index f8b390a9d9fb..9d4ef65da7f3 100644
>>> --- a/arch/powerpc/platforms/pseries/ras.c
>>> +++ b/arch/powerpc/platforms/pseries/ras.c
>>> @@ -699,7 +699,7 @@ static int mce_handle_err_virtmode(struct pt_regs *regs,
>>> mce_err.error_type = MCE_ERROR_TYPE_DCACHE;
>>> break;
>>> case MC_ERROR_TYPE_I_CACHE:
>>> - mce_err.error_type = MCE_ERROR_TYPE_DCACHE;
>>> + mce_err.error_type = MCE_ERROR_TYPE_ICACHE;
>>> break;
>>> case MC_ERROR_TYPE_UNKNOWN:
>>> default:
>>> --
>>> 2.26.2
next prev parent reply other threads:[~2021-04-19 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 12:57 [PATCH] powerpc/pseries/mce: Fix a typo in error type assignment Ganesh Goudar
2021-04-17 12:36 ` Michael Ellerman
2021-04-19 9:29 ` Ganesh
2021-04-19 12:39 ` Michael Ellerman [this message]
2021-04-21 13:08 ` 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=87y2decusl.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ganeshgr@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--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).