mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "M K, Muralidhara" <muralimk@amd.com>
To: Borislav Petkov <bp@alien8.de>, Yazen Ghannam <yazen.ghannam@amd.com>
Cc: 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 0/2] FRU Memory Poison Manager
Date: Tue, 20 Feb 2024 22:40:32 +0530	[thread overview]
Message-ID: <a91d1dfd-f29f-1afd-c42e-b681450db052@amd.com> (raw)
In-Reply-To: <953d9c1a-b504-cde5-5de1-2ce9b838204a@amd.com>



On 2/20/2024 5:59 PM, M K, Muralidhara wrote:
> 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@amd.com
> Signed-off-by: naveenkrishna.chatradhi@amd.com
> Co-developed-by: muralidhara.mk@amd.com
> Signed-off-by: muralidhara.mk@amd.com
> Co-developed-by: sathyapriya.k@amd.com
> Signed-off-by: sathyapriya.k@amd.com
> 
>
Sorry, Just re-arranging the tags. Please add the below tags

Co-developed-by: naveenkrishna.chatradhi@amd.com
Signed-off-by: naveenkrishna.chatradhi@amd.com
Co-developed-by: muralidhara.mk@amd.com
Signed-off-by: muralidhara.mk@amd.com
Tested-by: sathyapriya.k@amd.com


>> Thx.
>>
>> -- 
>> Regards/Gruss,
>>      Boris.
>>
>> https://people.kernel.org/tglx/notes-about-netiquette
>>

      reply	other threads:[~2024-02-20 17:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  3:35 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
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 [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=a91d1dfd-f29f-1afd-c42e-b681450db052@amd.com \
    --to=muralimk@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 \
    --cc=yazen.ghannam@amd.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®