From: Jens Axboe <axboe@kernel.dk>
To: Puthikorn Voravootivat <puthik@chromium.org>
Cc: FIO List <fio@vger.kernel.org>,
Gwendal Grignou <gwendal@chromium.org>,
Grant Grundler <grundler@chromium.org>
Subject: Re: [PATCH] Fix verify_only option not working properly
Date: Mon, 03 Mar 2014 15:52:49 -0800 [thread overview]
Message-ID: <531515D1.40904@kernel.dk> (raw)
In-Reply-To: <1393889612-14391-1-git-send-email-puthik@chromium.org>
On 2014-03-03 15:33, Puthikorn Voravootivat wrote:
> In commit c4b6117, we changed the place to call log_io_piece but
> the new place won't be reached when using verify_only option so
> that when we run with the verify_only option, fio won't verify
> anything at all.
>
> This patch fix that by also call the log_io_piece in the do_dry_run
> function for the verify_only code path.
Thanks applied, and with that patch, I've tagged 2.1.6 just now.
--
Jens Axboe
prev parent reply other threads:[~2014-03-03 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 23:33 [PATCH] Fix verify_only option not working properly Puthikorn Voravootivat
2014-03-03 23:52 ` Jens Axboe [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=531515D1.40904@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=grundler@chromium.org \
--cc=gwendal@chromium.org \
--cc=puthik@chromium.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