From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Smita.KoralahalliChannabasappa@amd.com, mchehab@kernel.org,
tony.luck@intel.com, james.morse@arm.com, rric@kernel.org
Subject: Re: [PATCH] EDAC/mc_sysfs: Increase legacy channel support to 12
Date: Tue, 1 Nov 2022 17:22:13 +0000 [thread overview]
Message-ID: <Y2FVxWXnleYkkTGL@yaz-fattaah> (raw)
In-Reply-To: <Y1+i5GvygCVfiCGx@zn.tnic>
On Mon, Oct 31, 2022 at 11:26:44AM +0100, Borislav Petkov wrote:
> On Tue, Oct 18, 2022 at 10:36:30AM -0500, Yazen Ghannam wrote:
> > Newer AMD systems, such as Genoa, can support up to 12 channels per EDAC
> > "mc" device. These are detected by the device's EDAC module, and the
> > current EDAC interface is properly enumerated. However, the legacy EDAC
> > sysfs interface provides device attributes only for channels 0 to 7.
> > Therefore, channels 8 to 11 will not be visible in the legacy interface.
> > This was overlooked in the initial support for AMD Genoa.
> >
> > Add additional device attributes so that up to 12 channels are visible
> > in the legacy EDAC sysfs interface.
> >
> > Ignore checkpatch warnings about "Symbolic permissions" to maintain
> > coding style.
> >
> > Fixes: e2be5955a886 ("EDAC/amd64: Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh")
> > Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
> > Cc: <stable@vger.kernel.org>
> > ---
> > drivers/edac/edac_mc_sysfs.c | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
>
> Applied, thanks.
>
Thank you!
-Yazen
prev parent reply other threads:[~2022-11-01 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:36 [PATCH] EDAC/mc_sysfs: Increase legacy channel support to 12 Yazen Ghannam
2022-10-31 10:26 ` Borislav Petkov
2022-11-01 17:22 ` Yazen Ghannam [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=Y2FVxWXnleYkkTGL@yaz-fattaah \
--to=yazen.ghannam@amd.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.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).