From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Vincent Fu <vincentfu@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"fio@vger.kernel.org" <fio@vger.kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Niklas Cassel <Niklas.Cassel@wdc.com>
Subject: Re: [PATCH v2 0/7] zbd: clean up code and fix bugs for open zones accounting
Date: Sat, 10 Jun 2023 00:10:11 +0000 [thread overview]
Message-ID: <gwk7twrqx3hcfmyat6m57virk553s46p6efuowd3eayag662oc@iyy57fioim7a> (raw)
In-Reply-To: <5271f7bf-a694-70e5-7cda-ec067b16b45b@gmail.com>
On Jun 09, 2023 / 09:48, Vincent Fu wrote:
[...]
> Shin'ichiro, yes the above patch silences the Coverity complaint. Would you
> send a patch for me to apply?
Thanks Vincent. Sure, I've sent it out.
prev parent reply other threads:[~2023-06-10 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 7:06 [PATCH v2 0/7] zbd: clean up code and fix bugs for open zones accounting Shin'ichiro Kawasaki
2023-06-08 7:06 ` [PATCH v2 1/7] zbd: rename 'open zones' to 'write zones' Shin'ichiro Kawasaki
2023-06-08 7:06 ` [PATCH v2 2/7] zbd: do not reset extra zones in open conditions Shin'ichiro Kawasaki
2023-06-08 7:06 ` [PATCH v2 3/7] zbd: fix write zone accounting of almost full zones Shin'ichiro Kawasaki
2023-06-08 7:06 ` [PATCH v2 4/7] zbd: fix write zone accounting of trim workload Shin'ichiro Kawasaki
2023-06-08 8:14 ` Niklas Cassel
2023-06-08 7:06 ` [PATCH v2 5/7] t/zbd: reset zones before tests with max_open_zones option Shin'ichiro Kawasaki
2023-06-08 7:06 ` [PATCH v2 6/7] t/zbd: test write zone accounting of almost full zones Shin'ichiro Kawasaki
2023-06-08 7:06 ` [PATCH v2 7/7] t/zbd: test write zone accounting of trim workload Shin'ichiro Kawasaki
2023-06-08 18:45 ` [PATCH v2 0/7] zbd: clean up code and fix bugs for open zones accounting Vincent Fu
2023-06-08 19:10 ` Jens Axboe
2023-06-09 3:09 ` Shinichiro Kawasaki
2023-06-09 13:48 ` Vincent Fu
2023-06-10 0:10 ` 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=gwk7twrqx3hcfmyat6m57virk553s46p6efuowd3eayag662oc@iyy57fioim7a \
--to=shinichiro.kawasaki@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=Niklas.Cassel@wdc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=vincentfu@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).