From: "Shah, Amit" <aams@amazon.de>
To: "Lawthers, Peter" <lawthers@amazon.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"Dannowski, Uwe" <uwed@amazon.de>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"jbeulich@suse.com" <jbeulich@suse.com>
Subject: Re: [PATCH] Propagate microcode update errors
Date: Fri, 16 Feb 2018 13:26:38 +0000 [thread overview]
Message-ID: <1518787598.5333.74.camel@amazon.com> (raw)
In-Reply-To: <1518787194-26405-1-git-send-email-lawthers@amazon.com>
On Fr, 2018-02-16 at 13:19 +0000, Peter Lawthers wrote:
> From: Uwe Dannowski <uwed@amazon.de>
>
> Errors on updating the microcode in the processor were silently
> dropped when invoked via the microcode_update hypercall. Also, the
> log
> message was misleading.
>
> Signed-off-by: Uwe Dannowski <uwed@amazon.de>
> Reviewed-by: Stefan Nuernberger <snu@amazon.de>
> Reviewed-by: Martin Pohlack <mpohlack@amazon.de>
> CC: David Woodhouse <dwmw@amazon.co.uk>
> CC: Amit Shah <aams@amazon.de>
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Amit Shah <aams@amazon.com>
--
Amit
Amazon Development Center Germany GmbH
Berlin - Dresden - Aachen
main office: Krausenstr. 38, 10117 Berlin
Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
Ust-ID: DE289237879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-02-16 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 13:19 [PATCH] Propagate microcode update errors Peter Lawthers
2018-02-16 13:25 ` Andrew Cooper
2018-02-16 13:26 ` Shah, Amit [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=1518787598.5333.74.camel@amazon.com \
--to=aams@amazon.de \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw@amazon.co.uk \
--cc=jbeulich@suse.com \
--cc=lawthers@amazon.com \
--cc=uwed@amazon.de \
--cc=xen-devel@lists.xenproject.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).