From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Christoph Hellwig <hch@lst.de>,
"Darrick J . Wong" <djwong@kernel.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v11 5/5] fscrypt: update documentation for direct I/O support
Date: Tue, 1 Feb 2022 09:07:23 +0100 [thread overview]
Message-ID: <20220201080723.GB29730@lst.de> (raw)
In-Reply-To: <20220128233940.79464-6-ebiggers@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2022-02-01 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 23:39 [PATCH v11 0/5] add support for direct I/O with fscrypt using blk-crypto Eric Biggers
2022-01-28 23:39 ` [PATCH v11 1/5] fscrypt: add functions for direct I/O support Eric Biggers
2022-02-01 8:06 ` Christoph Hellwig
2022-01-28 23:39 ` [PATCH v11 2/5] iomap: support direct I/O with fscrypt using blk-crypto Eric Biggers
2022-01-28 23:39 ` [PATCH v11 3/5] ext4: " Eric Biggers
2022-01-28 23:39 ` [PATCH v11 4/5] f2fs: " Eric Biggers
2022-01-29 0:27 ` Jaegeuk Kim
2022-01-28 23:39 ` [PATCH v11 5/5] fscrypt: update documentation for direct I/O support Eric Biggers
2022-02-01 8:07 ` Christoph Hellwig [this message]
2022-02-11 6:17 ` [PATCH v11 0/5] add support for direct I/O with fscrypt using blk-crypto Eric Biggers
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=20220201080723.GB29730@lst.de \
--to=hch@lst.de \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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).