From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Connor Kuehl <ckuehl@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH 0/2] [RESEND] SEV firmware error list touchups
Date: Thu, 27 May 2021 23:36:26 +0200 [thread overview]
Message-ID: <CAP+75-WxB3aKHC51gEF+vR0T9iEvkfC7mwJk+GdJEp8HpqhqYw@mail.gmail.com> (raw)
In-Reply-To: <4988c9d5-27e4-62ce-6f4b-96c3ca2de4d5@redhat.com>
ping^3...
On Tue, May 11, 2021 at 9:35 AM Philippe Mathieu-Daudé
<philmd@redhat.com> wrote:
>
> Cc'ing qemu-trivial@
>
> On 4/30/21 3:48 PM, Connor Kuehl wrote:
> > Connor Kuehl (2):
> > sev: use explicit indices for mapping firmware error codes to strings
> > sev: add missing firmware error conditions
> >
> > target/i386/sev.c | 48 ++++++++++++++++++++++++-----------------------
> > 1 file changed, 25 insertions(+), 23 deletions(-)
> >
>
next prev parent reply other threads:[~2021-05-27 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 13:48 [PATCH 0/2] [RESEND] SEV firmware error list touchups Connor Kuehl
2021-04-30 13:48 ` [PATCH 1/2] [RESEND] sev: use explicit indices for mapping firmware error codes to strings Connor Kuehl
2021-04-30 13:48 ` [PATCH 2/2] [RESEND] sev: add missing firmware error conditions Connor Kuehl
2021-05-11 7:35 ` [PATCH 0/2] [RESEND] SEV firmware error list touchups Philippe Mathieu-Daudé
2021-05-27 21:36 ` Philippe Mathieu-Daudé [this message]
2021-05-31 20:09 ` Eduardo Habkost
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=CAP+75-WxB3aKHC51gEF+vR0T9iEvkfC7mwJk+GdJEp8HpqhqYw@mail.gmail.com \
--to=philmd@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=ckuehl@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thomas.lendacky@amd.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 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.