From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: "chaitanyak@nvidia.com" <chaitanyak@nvidia.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH V2 blktests 0/3] fix and improvement for xfs log size change from new xfsprogs version
Date: Fri, 4 Nov 2022 11:42:12 +0000 [thread overview]
Message-ID: <20221104114212.vi45fza33ytlsgbx@shindev> (raw)
In-Reply-To: <20221102025702.1664101-1-yi.zhang@redhat.com>
On Nov 02, 2022 / 10:56, Yi Zhang wrote:
> Hi
>
> The first patch addressed nvme/012 nvme/013 failure which introduced
> from xfsprogs v5.19.0, the minimun xfs log size change to 64m
>
> The second patch introduced one new function _require_test_dev_size_mb
>
> The third patch add one new parameter to _run_fio_verify_io, this will
> allow fio I/O size definition to the test case
Have applied the patches. Please note that I took a liberty to do minor edits in
the second patch. Thanks!
--
Shin'ichiro Kawasaki
prev parent reply other threads:[~2022-11-04 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 2:56 [PATCH V2 blktests 0/3] fix and improvement for xfs log size change from new xfsprogs version Yi Zhang
2022-11-02 2:57 ` [PATCH V2 blktests 1/3] common/xfs: set the minimal log size 64m during mkfs.xfs Yi Zhang
2022-11-02 2:57 ` [PATCH V2 blktests 2/3] common/rc: add one function to check required dev size for TEST_DEV Yi Zhang
2022-11-02 2:57 ` [PATCH V2 blktests 3/3] nvme/012,013,035: change fio I/O size and move size definition place Yi Zhang
2022-11-02 5:43 ` [PATCH V2 blktests 0/3] fix and improvement for xfs log size change from new xfsprogs version Chaitanya Kulkarni
2022-11-04 11:42 ` Shinichiro Kawasaki [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=20221104114212.vi45fza33ytlsgbx@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=yi.zhang@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