From: Satya Tangirala <satyat@google.com>
To: "Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2 2/3] fscrypt: Add metadata encryption support
Date: Thu, 17 Dec 2020 15:24:37 +0000 [thread overview]
Message-ID: <X9t4NXGM7cbxsimQ@google.com> (raw)
In-Reply-To: <20201217150435.1505269-3-satyat@google.com>
I'm not yet done with the xfstests that Eric asked for - I'll send them
out as soon as they're done.
WARNING: multiple messages have this Message-ID (diff)
From: Satya Tangirala via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: "Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 2/3] fscrypt: Add metadata encryption support
Date: Thu, 17 Dec 2020 15:24:37 +0000 [thread overview]
Message-ID: <X9t4NXGM7cbxsimQ@google.com> (raw)
In-Reply-To: <20201217150435.1505269-3-satyat@google.com>
I'm not yet done with the xfstests that Eric asked for - I'll send them
out as soon as they're done.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-12-17 15:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:04 [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala
2020-12-17 15:04 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-12-17 15:04 ` [PATCH v2 1/3] fscrypt, f2fs: replace fscrypt_get_devices with fscrypt_get_device Satya Tangirala
2020-12-17 15:04 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-12-17 15:04 ` [PATCH v2 2/3] fscrypt: Add metadata encryption support Satya Tangirala
2020-12-17 15:04 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-12-17 15:24 ` Satya Tangirala [this message]
2020-12-17 15:24 ` Satya Tangirala via Linux-f2fs-devel
2020-12-24 11:31 ` Satya Tangirala
2020-12-24 11:31 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2021-01-29 20:41 ` Eric Biggers
2021-01-29 20:41 ` [f2fs-dev] " Eric Biggers
2020-12-17 15:04 ` [PATCH v2 3/3] f2fs: " Satya Tangirala
2020-12-17 15:04 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2021-01-29 20:57 ` Eric Biggers
2021-01-29 20:57 ` [f2fs-dev] " Eric Biggers
2020-12-17 15:16 ` [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala
2020-12-17 15:16 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-12-17 18:08 ` Theodore Y. Ts'o
2020-12-17 18:08 ` [f2fs-dev] " Theodore Y. Ts'o
2020-12-17 20:51 ` Satya Tangirala
2020-12-17 20:51 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
2020-12-17 23:34 ` Theodore Y. Ts'o
2020-12-17 23:34 ` [f2fs-dev] " Theodore Y. Ts'o
2020-12-18 0:05 ` Satya Tangirala
2020-12-18 0:05 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel
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=X9t4NXGM7cbxsimQ@google.com \
--to=satyat@google.com \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.