From: Yazen Ghannam <yazen.ghannam@amd.com>
To: "Luck, Tony" <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: yazen.ghannam@amd.com, "x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: Re: [PATCH v2] x86/mce: Always call memory_failure() when there is a valid address
Date: Wed, 19 Apr 2023 09:08:00 -0400 [thread overview]
Message-ID: <0bf7ed90-7231-d280-fd52-5906d693fbe1@amd.com> (raw)
In-Reply-To: <SJ1PR11MB6083BF7037C9C86E097FCAA0FC9D9@SJ1PR11MB6083.namprd11.prod.outlook.com>
On 4/18/23 15:34, Luck, Tony wrote:
>>> + if (mce_usable_address(&m))
>>
>> This should be !mce_usable_address().
>
>> Copying old patch here. Feel free to reuse any of the commit message if
>> it helps.
>
> Might as well just take your version. The commit message seems fine.
>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
>
Thanks!
>
>> From: Yazen Ghannam <yazen.ghannam@amd.com>
>> Date: Fri, 8 Jan 2021 04:00:35 +0000
>
> 2021 - wow!
>
Yeah, I've been distracted lately with other things. >_>
-Yazen
prev parent reply other threads:[~2023-04-19 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 0:51 [PATCH] x86/mce: Check that memory address is usable for recovery Tony Luck
2023-04-18 16:41 ` Yazen Ghannam
2023-04-18 17:27 ` Tony Luck
2023-04-18 17:51 ` Yazen Ghannam
2023-04-18 18:23 ` Tony Luck
2023-04-18 18:03 ` [PATCH v2] x86/mce: Always call memory_failure() when there is a valid address Tony Luck
2023-04-18 18:17 ` Yazen Ghannam
2023-04-18 19:34 ` Luck, Tony
2023-04-19 13:08 ` 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=0bf7ed90-7231-d280-fd52-5906d693fbe1@amd.com \
--to=yazen.ghannam@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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).