From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: linux-fsdevel@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 3/3] zonefs: fix zonefs_iomap_begin() for reads
Date: Wed, 8 Jun 2022 07:49:58 +0200 [thread overview]
Message-ID: <20220608054958.GA7022@lst.de> (raw)
In-Reply-To: <20220608045627.142408-4-damien.lemoal@opensource.wdc.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2022-06-08 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:56 [PATCH v2 0/3] zonefs fixes Damien Le Moal
2022-06-08 4:56 ` [PATCH v2 1/3] zonefs: fix handling of explicit_open option on mount Damien Le Moal
2022-06-08 4:56 ` [PATCH v2 2/3] zonefs: Do not ignore explicit_open with active zone limit Damien Le Moal
2022-06-08 4:56 ` [PATCH v2 3/3] zonefs: fix zonefs_iomap_begin() for reads Damien Le Moal
2022-06-08 5:49 ` Christoph Hellwig [this message]
2022-06-08 8:35 ` Johannes Thumshirn
2022-06-08 9:01 ` Jørgen Hansen
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=20220608054958.GA7022@lst.de \
--to=hch@lst.de \
--cc=damien.lemoal@opensource.wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).