From: Max Reitz <mreitz@redhat.com>
To: Tao Xu <tao3.xu@intel.com>, kwolf@redhat.com
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH] iotests: Fix typo in iotest 051
Date: Thu, 25 Mar 2021 16:03:41 +0100 [thread overview]
Message-ID: <67af455e-74f2-000e-e509-ab5b742d0319@redhat.com> (raw)
In-Reply-To: <20210324084321.90952-1-tao3.xu@intel.com>
On 24.03.21 09:43, Tao Xu wrote:
> There is an typo in iotest 051, correct it.
>
> Signed-off-by: Tao Xu <tao3.xu@intel.com>
> ---
> tests/qemu-iotests/051 | 2 +-
> tests/qemu-iotests/051.pc.out | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Thanks, applied to my block branch:
https://git.xanclic.moe/XanClic/qemu/commits/branch/block
(For the record: 051.out is not touched, which is correct because the
affected branch is only taken for $QEMU_DEFAULT_MACHINE == pc.)
prev parent reply other threads:[~2021-03-25 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 8:43 [PATCH] iotests: Fix typo in iotest 051 Tao Xu
2021-03-25 15:03 ` Max Reitz [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=67af455e-74f2-000e-e509-ab5b742d0319@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tao3.xu@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;
as well as URLs for NNTP newsgroup(s).