[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5fb57072-96a6-4ce9-8636-f1746693cfff@linux.alibaba.com>
Date: Wed, 12 Feb 2025 09:51:59 +0800
From: Shuai Xue <xueshuai@...ux.alibaba.com>
To: "Luck, Tony" <tony.luck@...el.com>, "bp@...en8.de" <bp@...en8.de>,
"nao.horiguchi@...il.com" <nao.horiguchi@...il.com>
Cc: "tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
"linmiaohe@...wei.com" <linmiaohe@...wei.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"baolin.wang@...ux.alibaba.com" <baolin.wang@...ux.alibaba.com>,
"tianruidong@...ux.alibaba.com" <tianruidong@...ux.alibaba.com>
Subject: Re: [PATCH v1 1/4] x86/mce: Collect error message for severities
below MCE_PANIC_SEVERITY
在 2025/2/12 00:51, Luck, Tony 写道:
>> + char *tmp = *msg, cur_sev = MCE_NO_SEVERITY, sev;
>
> Should cur_sev and sev be of type "int" (since that's the type returned by mce_severity())?
>
> It doesn't matter today since the list of return value does fit into "char", but it is setting up
> to fail if that should ever change.
>
> -Tony
You are right, I previously only focused on the fact that the field 'sev' of
struct severity is an unsigned char.
Will fix it in next version.
Thanks.
Shuai
Powered by blists - more mailing lists