From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, hpa@zytor.com,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v5 2/2] x86/mce: Add support for Extended Physical Address MCA changes
Date: Tue, 12 Jul 2022 13:51:25 +0000 [thread overview]
Message-ID: <Ys18XVCB7CeR/jVw@yaz-fattaah> (raw)
In-Reply-To: <YrnTMmwl5TrHwT9J@zn.tnic>
On Mon, Jun 27, 2022 at 05:56:34PM +0200, Borislav Petkov wrote:
> On Thu, Jun 09, 2022 at 07:19:29PM +0000, Yazen Ghannam wrote:
> > Also, please see the patch below which is based on Boris' patch from earlier
> > in this thread.
>
> Looks good to me. You can send me one against latest tip:ras/core
> whenever you can.
>
Thanks. Do you want a set with yours, mine, and Smita's patches all together?
-Yazen
next prev parent reply other threads:[~2022-07-12 13:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 15:40 [PATCH v5 0/2] x86/mce: Support extended MCA_ADDR address on SMCA systems Smita Koralahalli
2022-04-12 15:40 ` [PATCH v5 1/2] x86/mce: Define function to extract ErrorAddr from MCA_ADDR Smita Koralahalli
2022-04-12 15:40 ` [PATCH v5 2/2] x86/mce: Add support for Extended Physical Address MCA changes Smita Koralahalli
2022-04-13 10:21 ` Borislav Petkov
2022-04-13 14:10 ` Yazen Ghannam
2022-04-13 14:54 ` Borislav Petkov
2022-04-13 15:59 ` Luck, Tony
2022-04-13 16:19 ` Borislav Petkov
2022-04-13 19:40 ` Yazen Ghannam
2022-04-14 9:11 ` Borislav Petkov
2022-04-15 14:56 ` Yazen Ghannam
2022-04-15 16:37 ` Luck, Tony
2022-06-09 19:19 ` Yazen Ghannam
2022-06-27 15:56 ` Borislav Petkov
2022-07-12 13:51 ` Yazen Ghannam [this message]
2022-07-12 14:08 ` Borislav Petkov
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=Ys18XVCB7CeR/jVw@yaz-fattaah \
--to=yazen.ghannam@amd.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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