From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Connor Kuehl <ckuehl@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/2] SEV firmware error list touchups
Date: Tue, 11 May 2021 09:36:15 +0200 [thread overview]
Message-ID: <CAP+75-UEA3ZeL10SwyG8k9C2BTwfTHPJ1oQ=NGJC54GW5gg1qw@mail.gmail.com> (raw)
In-Reply-To: <20210322164327.GX3139005@habkost.net>
On Mon, Mar 22, 2021 at 5:43 PM Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Mon, Mar 22, 2021 at 09:09:44AM -0500, Connor Kuehl wrote:
> > On 3/22/21 5:18 AM, Philippe Mathieu-Daudé wrote:
> > > On 3/15/21 3:08 PM, Connor Kuehl wrote:
> > > > On 2/18/21 9:16 AM, 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(-)
> > > > >
> > > >
> > > > Eduardo, Paolo, Richard: ping
> > >
> > > Looks too late for 6.0 now.
> > >
> > > Can you repost/ping after QEMU 6.0 is release?
> >
> > Sure.
>
> My apologies for not replying before and not reviewing or merging
> this in time for 6.0.
FYI there is a RESEND:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg803017.html
prev parent reply other threads:[~2021-05-11 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 15:16 [PATCH 0/2] SEV firmware error list touchups Connor Kuehl
2021-02-18 15:16 ` [PATCH 1/2] sev: use explicit indices for mapping firmware error codes to strings Connor Kuehl
2021-02-18 15:16 ` [PATCH 2/2] sev: add missing firmware error conditions Connor Kuehl
2021-02-18 15:48 ` [PATCH 0/2] SEV firmware error list touchups Philippe Mathieu-Daudé
2021-02-19 14:46 ` Connor Kuehl
2021-02-19 17:57 ` Philippe Mathieu-Daudé
2021-03-08 16:41 ` Connor Kuehl
2021-03-15 14:08 ` Connor Kuehl
2021-03-22 10:18 ` Philippe Mathieu-Daudé
2021-03-22 14:09 ` Connor Kuehl
2021-03-22 16:43 ` Eduardo Habkost
2021-05-11 7:36 ` Philippe Mathieu-Daudé [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='CAP+75-UEA3ZeL10SwyG8k9C2BTwfTHPJ1oQ=NGJC54GW5gg1qw@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=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.