All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Yazen Ghannam <Yazen.Ghannam@amd.com>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/5] x86/mce: Remove indirect calls
Date: Wed, 22 Sep 2021 13:35:09 -0700	[thread overview]
Message-ID: <YUuTfd/NmrNPgkqM@agluck-desk2.amr.corp.intel.com> (raw)
In-Reply-To: <20210922165101.18951-1-bp@alien8.de>

On Wed, Sep 22, 2021 at 06:50:56PM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
> 
> Hi,
> 
> here's v1 with all review comments addressed.

Looks good to me.

Reviewed-by: Tony Luck <tony.luck@intel.com>

Some light testing of injection/recovery still
works too.

-Tony

  parent reply	other threads:[~2021-09-22 20:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 16:50 [PATCH v1 0/5] x86/mce: Remove indirect calls Borislav Petkov
2021-09-22 16:50 ` [PATCH v1 1/5] x86/mce: Get rid of the mce_severity function pointer Borislav Petkov
2021-09-23  9:50   ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2021-09-22 16:50 ` [PATCH v1 2/5] x86/mce: Get rid of machine_check_vector Borislav Petkov
2021-09-23  9:50   ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2021-09-22 16:50 ` [PATCH v1 3/5] x86/mce: Get rid of msr_ops Borislav Petkov
2021-09-23  9:50   ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2021-09-22 16:51 ` [PATCH v1 4/5] x86/mce: Get rid of the ->quirk_no_way_out() indirect call Borislav Petkov
2021-09-23  9:50   ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2021-09-22 16:51 ` [PATCH v1 5/5] x86/mce: Sort mca_config members to get rid of unnecessary padding Borislav Petkov
2021-09-23  9:50   ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2021-09-22 20:35 ` Luck, Tony [this message]
2021-09-22 20:42   ` [PATCH v1 0/5] x86/mce: Remove indirect calls 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=YUuTfd/NmrNPgkqM@agluck-desk2.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=Yazen.Ghannam@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.