From: Chao Yu <chao@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Lukas Czerner <lczerner@redhat.com>,
Jeff Layton <jlayton@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH v3 4/5] f2fs: use the updated test_dummy_encryption helper functions
Date: Thu, 19 May 2022 19:21:56 +0800 [thread overview]
Message-ID: <5c9b94f4-28f4-9f3c-8cc7-b0b09270b91a@kernel.org> (raw)
In-Reply-To: <20220513231605.175121-5-ebiggers@kernel.org>
On 2022/5/14 7:16, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Switch f2fs over to the functions that are replacing
> fscrypt_set_test_dummy_encryption(). Since f2fs hasn't been converted
> to the new mount API yet, this doesn't really provide a benefit for
> f2fs. But it allows fscrypt_set_test_dummy_encryption() to be removed.
>
> Also take the opportunity to eliminate an #ifdef.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Lukas Czerner <lczerner@redhat.com>,
Jeff Layton <jlayton@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH v3 4/5] f2fs: use the updated test_dummy_encryption helper functions
Date: Thu, 19 May 2022 19:21:56 +0800 [thread overview]
Message-ID: <5c9b94f4-28f4-9f3c-8cc7-b0b09270b91a@kernel.org> (raw)
In-Reply-To: <20220513231605.175121-5-ebiggers@kernel.org>
On 2022/5/14 7:16, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Switch f2fs over to the functions that are replacing
> fscrypt_set_test_dummy_encryption(). Since f2fs hasn't been converted
> to the new mount API yet, this doesn't really provide a benefit for
> f2fs. But it allows fscrypt_set_test_dummy_encryption() to be removed.
>
> Also take the opportunity to eliminate an #ifdef.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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:[~2022-05-19 11:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 23:16 [f2fs-dev] [PATCH v3 0/5] test_dummy_encryption fixes and cleanups Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 1/5] ext4: fix memory leak in parse_apply_sb_mount_options() Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-14 12:09 ` [f2fs-dev] " Ritesh Harjani
2022-05-14 12:09 ` Ritesh Harjani
2022-05-19 2:10 ` Theodore Ts'o
2022-05-19 2:10 ` [f2fs-dev] " Theodore Ts'o
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 2/5] ext4: only allow test_dummy_encryption when supported Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-19 2:11 ` Theodore Ts'o
2022-05-19 2:11 ` [f2fs-dev] " Theodore Ts'o
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 3/5] ext4: fix up test_dummy_encryption handling for new mount API Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 4/5] f2fs: use the updated test_dummy_encryption helper functions Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-19 11:21 ` Chao Yu [this message]
2022-05-19 11:21 ` [f2fs-dev] " Chao Yu
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 5/5] fscrypt: remove fscrypt_set_test_dummy_encryption() Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-08-15 18:48 ` [f2fs-dev] " Eric Biggers
2022-08-15 18:48 ` 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=5c9b94f4-28f4-9f3c-8cc7-b0b09270b91a@kernel.org \
--to=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jlayton@kernel.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@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.