[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <953d9c1a-b504-cde5-5de1-2ce9b838204a@amd.com>
Date: Tue, 20 Feb 2024 17:59:37 +0530
From: "M K, Muralidhara" <muralimk@....com>
To: Borislav Petkov <bp@...en8.de>, Yazen Ghannam <yazen.ghannam@....com>
Cc: tony.luck@...el.com, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, avadhut.naik@....com, john.allen@....com,
muralidhara.mk@....com, naveenkrishna.chatradhi@....com,
sathyapriya.k@....com
Subject: Re: [PATCH 0/2] FRU Memory Poison Manager
Hi Boris,
On 2/14/2024 1:22 PM, Borislav Petkov wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Tue, Feb 13, 2024 at 09:35:14PM -0600, Yazen Ghannam wrote:
>> I included questions in code comments where I think more attention is
>> needed.
>
> Lemme look.
>
>> Also, I kept Naveen as a maintainer in case he's still interested.
>
> I don't mind that as long as he responds to bug reports from users and
> addresses them in timely manner.
>
>> I did some basic testing on a 2P server system without ERST support.
>> Mostly I tried to check out the memory layout of the structures. And I
>> did some memory error injections to check out the record updating flow.
>> I did some fixups after testing, so I apologize if I missed anything.
>
> Right, I'd like for Murali and/or Naveen to test the final version but
> lemme go through them first.
>
Please include, we have worked previous versions of this patch set.
Co-developed-by: naveenkrishna.chatradhi@....com
Signed-off-by: naveenkrishna.chatradhi@....com
Co-developed-by: muralidhara.mk@....com
Signed-off-by: muralidhara.mk@....com
Co-developed-by: sathyapriya.k@....com
Signed-off-by: sathyapriya.k@....com
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
Powered by blists - more mailing lists