From: Hyman Huang <yong.huang@smartx.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
yong.huang@smartx.com
Subject: [PATCH v2 0/2] Nitpick at the error message's output
Date: Sun, 7 Jan 2024 19:53:09 +0800 [thread overview]
Message-ID: <cover.1704626686.git.yong.huang@smartx.com> (raw)
v2:
- rebase on master
- add a commit to sort the error message so that an explanation
error number can be returned on all failure paths
Hyman Huang (2):
i386/sev: Sort the error message
i386/sev: Nitpick at the error message's output
target/i386/sev.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
2.39.1
next reply other threads:[~2024-01-07 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 11:53 Hyman Huang [this message]
2024-01-07 11:53 ` [PATCH v2 1/2] i386/sev: Sort the error message Hyman Huang
2024-01-07 11:53 ` [PATCH v2 2/2] i386/sev: Nitpick at the error message's output Hyman Huang
2024-01-15 6:26 ` [PATCH v2 0/2] " Yong Huang
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=cover.1704626686.git.yong.huang@smartx.com \
--to=yong.huang@smartx.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).