From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Guixiong Wei <weiguixiong@bytedance.com>
Cc: Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
Muralidhara M K <muralidhara.mk@amd.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] EDAC/mce_amd: Add missing long names for SMCA bank types
Date: Mon, 12 Oct 2026 10:03:30 -0400 [thread overview]
Message-ID: <20261012140330.GC15198@yaz-khff2.amd.com> (raw)
In-Reply-To: <20261009020447.90758-2-weiguixiong@bytedance.com>
On Fri, Oct 09, 2026 at 10:04:24AM +0800, Guixiong Wei wrote:
> Commit 47b744ea5e3c ("x86/MCE/AMD: Add new MA_LLC, USR_DP,
> and USR_CP bank types") added three SMCA bank types after the bank long
> names had been moved to the MCE decoder.
>
> The new types were added to the enum, short-name table, and HWID/McaType
> mapping, but not to smca_long_names[]. As a result, an error from any of
> these banks is logged with "(null)" in place of the bank name.
>
> Add the missing long names.
>
> Fixes: 47b744ea5e3c ("x86/MCE/AMD: Add new MA_LLC, USR_DP, and USR_CP bank types")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guixiong Wei <weiguixiong@bytedance.com>
These were intentionaly left out as it as it seems users have been
moving to user space decode tools.
Do you actually need these in the kernel?
Thanks,
Yazen
next prev parent reply other threads:[~2026-10-12 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 2:04 [PATCH] EDAC/mce_amd: Add missing long names for SMCA bank types Guixiong Wei
2026-10-09 5:07 ` Borislav Petkov
2026-10-12 14:03 ` Yazen Ghannam [this message]
2026-10-17 19:51 ` Borislav Petkov
2026-10-18 22:34 ` Yazen Ghannam
2026-10-18 23:07 ` Borislav Petkov
2026-10-19 2:16 ` Guixiong Wei
2026-10-19 4:19 ` Borislav Petkov
2026-10-19 13:05 ` Yazen Ghannam
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=20261012140330.GC15198@yaz-khff2.amd.com \
--to=yazen.ghannam@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=weiguixiong@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.