From: Satya Tangirala <satyaprateek2357@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Satya Tangirala <satyat@google.com>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>, Chao Yu <chao@kernel.org>,
Jens Axboe <axboe@kernel.dk>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
open list <linux-kernel@vger.kernel.org>,
linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH v8 0/8] add support for direct I/O with fscrypt using blk-crypto
Date: Tue, 8 Jun 2021 19:45:56 -0700 [thread overview]
Message-ID: <20210609024556.GA11153@fractal> (raw)
In-Reply-To: <20210526080224.GI4005783@dell>
On Wed, May 26, 2021 at 09:02:24AM +0100, Lee Jones wrote:
> On Tue, 25 May 2021, Satya Tangirala wrote:
> 65;6200;1c
> > On Tue, May 25, 2021 at 01:57:28PM +0100, Lee Jones wrote:
> > > On Thu, 21 Jan 2021 at 23:06, Satya Tangirala <satyat@google.com> wrote:
> > >
> > > > This patch series adds support for direct I/O with fscrypt using
> > > > blk-crypto.
> > > >
> > >
> > > Is there an update on this set please?
> > >
> > > I can't seem to find any reviews or follow-up since v8 was posted back in
> > > January.
> > >
> > This patchset relies on the block layer fixes patchset here
> > https://lore.kernel.org/linux-block/20210325212609.492188-1-satyat@google.com/
> > That said, I haven't been able to actively work on both the patchsets
> > for a while, but I'll send out updates for both patchsets over the
> > next week or so.
>
> Thanks Satya, I'd appreciate that.
FYI I sent out an updated patch series last week at
https://lore.kernel.org/linux-fscrypt/20210604210908.2105870-1-satyat@google.com/
next prev parent reply other threads:[~2021-06-09 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 23:03 [PATCH v8 0/8] add support for direct I/O with fscrypt using blk-crypto Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 1/8] block: blk-crypto-fallback: handle data unit split across multiple bvecs Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 2/8] block: blk-crypto: relax alignment requirements for bvecs in bios Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 3/8] fscrypt: add functions for direct I/O support Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 4/8] direct-io: add support for fscrypt using blk-crypto Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 5/8] iomap: support direct I/O with " Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 6/8] ext4: " Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 7/8] f2fs: " Satya Tangirala
2021-01-21 23:03 ` [PATCH v8 8/8] fscrypt: update documentation for direct I/O support Satya Tangirala
[not found] ` <CAF2Aj3jbEnnG1-bHARSt6xF12VKttg7Bt52gV=bEQUkaspDC9w@mail.gmail.com>
2021-05-25 18:10 ` [PATCH v8 0/8] add support for direct I/O with fscrypt using blk-crypto Satya Tangirala
2021-05-26 8:02 ` Lee Jones
2021-06-09 2:45 ` Satya Tangirala [this message]
2021-06-30 9:47 ` Lee Jones
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=20210609024556.GA11153@fractal \
--to=satyaprateek2357@gmail.com \
--cc=axboe@kernel.dk \
--cc=chao@kernel.org \
--cc=darrick.wong@oracle.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=satyat@google.com \
--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).