From: Boris Petkov <bp@alien8.de>
To: Oleksandr Natalenko <oleksandr@natalenko.name>,
"Luck, Tony" <tony.luck@intel.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
sironi@amazon.de
Subject: Re: [PATCH v2] arch/x86: Fix boot_cpu_data.microcode version output
Date: Wed, 01 Aug 2018 19:14:49 +0300 [thread overview]
Message-ID: <D0F737F0-64AD-4F61-86B3-F8FFA9C6B9BA@alien8.de> (raw)
In-Reply-To: <84058a7359c55f2af16a85398df85a36@natalenko.name>
On August 1, 2018 7:01:50 PM GMT+03:00, Oleksandr Natalenko <oleksandr@natalenko.name> wrote:
>I don't mind doing the right thing at all. It is just to inform you
>that
>it was found to be useful.
I don't think it would've worked if you did a second microcode upgrade on the system.
--
Sent from a small device: formatting sux and brevity is inevitable.
next prev parent reply other threads:[~2018-08-01 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20180731112739.32338-1-prarit@redhat.com>
2018-08-01 6:38 ` Oleksandr Natalenko
2018-08-01 11:38 ` Prarit Bhargava
2018-08-01 14:16 ` Oleksandr Natalenko
2018-08-01 15:29 ` Borislav Petkov
2018-08-01 15:59 ` Luck, Tony
2018-08-01 16:01 ` Oleksandr Natalenko
2018-08-01 16:14 ` Boris Petkov [this message]
2018-06-01 12:19 [PATCH] x86/MCE: Get microcode revision from cpu_info instead of boot_cpu_data Borislav Petkov
2018-07-31 11:27 ` [PATCH v2] arch/x86: Fix boot_cpu_data.microcode version output Prarit Bhargava
2018-07-31 11:46 ` Sironi, Filippo
2018-07-31 13:00 ` Borislav Petkov
2018-07-31 15:31 ` Sironi, Filippo
2018-08-01 15:43 ` Borislav Petkov
2018-08-01 15:55 ` Prarit Bhargava
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=D0F737F0-64AD-4F61-86B3-F8FFA9C6B9BA@alien8.de \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=prarit@redhat.com \
--cc=sironi@amazon.de \
--cc=tony.luck@intel.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®