From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: yazen.ghannam@amd.com, tony.luck@intel.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
avadhut.naik@amd.com, john.allen@amd.com, muralidhara.mk@amd.com,
naveenkrishna.chatradhi@amd.com, sathyapriya.k@amd.com
Subject: Re: [PATCH 2/2] RAS: Introduce the FRU Memory Poison Manager
Date: Wed, 14 Feb 2024 09:46:46 -0500 [thread overview]
Message-ID: <3bc7bef5-9cfc-400a-a1ba-99ebf5d94952@amd.com> (raw)
In-Reply-To: <20240214103446.GDZcyXRkyf1bFzMh7L@fat_crate.local>
On 2/14/2024 5:34 AM, Borislav Petkov wrote:
> On Tue, Feb 13, 2024 at 09:35:16PM -0600, Yazen Ghannam wrote:
>> +#include <asm/mce.h>
>
> ...
>
>> +static void init_fpd(struct cper_fru_poison_desc *fpd, struct mce *m)
> ^^^^^^
>
>
> This is a generic thing and thus can't use an x86-ism struct mce,
> remember?
>
Yep, that's one of the assumptions/limitations I highlighted.
Thanks,
Yazen
next prev parent reply other threads:[~2024-02-14 14:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 3:35 [PATCH 0/2] " Yazen Ghannam
2024-02-14 3:35 ` [PATCH 1/2] RAS/AMD/ATL, EDAC/amd64: Move MI300 Row Retirement to ATL Yazen Ghannam
2024-02-14 8:36 ` Borislav Petkov
2024-02-14 14:19 ` Yazen Ghannam
2024-02-14 16:05 ` Borislav Petkov
2024-02-14 3:35 ` [PATCH 2/2] RAS: Introduce the FRU Memory Poison Manager Yazen Ghannam
2024-02-14 9:06 ` Borislav Petkov
2024-02-14 14:21 ` Yazen Ghannam
2024-02-14 15:49 ` Borislav Petkov
2024-02-14 16:01 ` Yazen Ghannam
2024-02-14 16:11 ` Borislav Petkov
2024-02-14 9:28 ` Borislav Petkov
2024-02-14 14:28 ` Yazen Ghannam
2024-02-14 17:50 ` Borislav Petkov
2024-02-14 18:21 ` Borislav Petkov
2024-02-14 10:29 ` Borislav Petkov
2024-02-14 14:45 ` Yazen Ghannam
2024-02-14 18:04 ` Borislav Petkov
2024-02-14 10:34 ` Borislav Petkov
2024-02-14 14:46 ` Yazen Ghannam [this message]
2024-02-14 18:29 ` Borislav Petkov
2024-02-14 10:51 ` Borislav Petkov
2024-02-14 14:49 ` Yazen Ghannam
2024-02-14 11:05 ` Borislav Petkov
2024-02-14 14:56 ` Yazen Ghannam
2024-02-14 18:44 ` Borislav Petkov
2024-02-14 11:10 ` Borislav Petkov
2024-02-14 14:57 ` Yazen Ghannam
2024-02-14 11:15 ` Borislav Petkov
2024-02-14 14:59 ` Yazen Ghannam
2024-02-14 11:36 ` Borislav Petkov
2024-02-14 15:26 ` Yazen Ghannam
2024-02-14 19:44 ` Borislav Petkov
2024-02-14 20:10 ` Borislav Petkov
2024-02-14 12:02 ` Borislav Petkov
2024-02-14 15:33 ` Yazen Ghannam
2024-02-14 20:18 ` Borislav Petkov
2024-02-14 18:47 ` Borislav Petkov
2024-02-14 7:52 ` [PATCH 0/2] " Borislav Petkov
2024-02-20 12:29 ` M K, Muralidhara
2024-02-20 17:10 ` M K, Muralidhara
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=3bc7bef5-9cfc-400a-a1ba-99ebf5d94952@amd.com \
--to=yazen.ghannam@amd.com \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=john.allen@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=sathyapriya.k@amd.com \
--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
all inboxes | Powered by JetHome®