From: Christoph Hellwig <hch@lst.de>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Christoph Hellwig <hch@lst.de>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: fix pattern for write test
Date: Tue, 14 Jul 2009 23:20:44 +0200 [thread overview]
Message-ID: <20090714212044.GA7580@lst.de> (raw)
In-Reply-To: <1247315696-5877-1-git-send-email-weil@mail.berlios.de>
On Sat, Jul 11, 2009 at 02:34:56PM +0200, Stefan Weil wrote:
> The write pattern value 0axb is invalid and evaluates to 0,
> so the read check (which uses a correct value of 0xab) will fail.
>
> This failure will only be detected with a separate patch for
> qemu-io. Without it, qemu-io cannot interpret hex values
> and always uses a pattern value of 0.
Thanks a lot, I've put this patch in.
prev parent reply other threads:[~2009-07-14 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 12:34 [Qemu-devel] [PATCH] qemu-iotests: fix pattern for write test Stefan Weil
2009-07-11 12:35 ` [Qemu-devel] [PATCH] qemu-io: Fix parsing of pattern arguments Stefan Weil
2009-07-14 21:24 ` Christoph Hellwig
2009-07-14 21:29 ` Stefan Weil
2009-07-14 21:20 ` Christoph Hellwig [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=20090714212044.GA7580@lst.de \
--to=hch@lst.de \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).