From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.3 0/2] block: Fix for trailing whitespace in qemu-img create and its tests
Date: Thu, 11 Dec 2014 08:21:07 +0800 [thread overview]
Message-ID: <20141211002107.GB3110@ad.nay.redhat.com> (raw)
In-Reply-To: <87oarbsm77.fsf@blackfin.pond.sub.org>
On Wed, 12/10 13:50, Markus Armbruster wrote:
> Fam Zheng <famz@redhat.com> writes:
>
> > This will make it easier to keep checkpatch.pl happy.
> >
> > Fam Zheng (2):
> > qemu-iotests: Remove traling whitespaces in *.out
> > block: Don't add trailing space in "Formating..." message
>
> Sounds like PATCH 1 breaks the test, and PATCH 2 unbreaks it. If that's
> the case, they need to be squashed.
No. Our qemu-iotests driver ignores ending space:
if diff -w "$reference" $tmp.out >/dev/null 2>&1
then
echo ""
if $err
then
:
else
echo "$seq `expr $stop - $start`" >>$tmp.time
fi
else
echo " - output mismatch (see $seq.out.bad)"
mv $tmp.out $seq.out.bad
$diff -w "$reference" $seq.out.bad
err=true
fi
Are you happy with the "sep" or do you want a full-fledged version?
Fam
next prev parent reply other threads:[~2014-12-11 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 7:38 [Qemu-devel] [PATCH for-2.3 0/2] block: Fix for trailing whitespace in qemu-img create and its tests Fam Zheng
2014-12-09 7:38 ` [Qemu-devel] [PATCH for-2.3 1/2] qemu-iotests: Remove traling whitespaces in *.out Fam Zheng
2014-12-09 7:38 ` [Qemu-devel] [PATCH for-2.3 2/2] block: Don't add trailing space in "Formating..." message Fam Zheng
2014-12-10 12:57 ` Markus Armbruster
2014-12-09 15:33 ` [Qemu-devel] [PATCH for-2.3 0/2] block: Fix for trailing whitespace in qemu-img create and its tests Eric Blake
2014-12-10 12:50 ` Markus Armbruster
2014-12-11 0:21 ` Fam Zheng [this message]
2014-12-11 8:43 ` Markus Armbruster
2014-12-12 16:55 ` Stefan Hajnoczi
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=20141211002107.GB3110@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).