From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH] fscrypt: move fscrypt_d_revalidate() to fname.c
Date: Fri, 3 Jan 2020 08:59:38 -0800 [thread overview]
Message-ID: <20200103165938.GG19521@gmail.com> (raw)
In-Reply-To: <20191209204359.228544-1-ebiggers@kernel.org>
On Mon, Dec 09, 2019 at 12:43:59PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> fscrypt_d_revalidate() and fscrypt_d_ops really belong in fname.c, since
> they're specific to filenames encryption. crypto.c is for contents
> encryption and general fs/crypto/ initialization and utilities.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> fs/crypto/crypto.c | 50 -------------------------------------
> fs/crypto/fname.c | 49 ++++++++++++++++++++++++++++++++++++
> fs/crypto/fscrypt_private.h | 2 +-
> 3 files changed, 50 insertions(+), 51 deletions(-)
Applied to fscrypt.git#master for 5.6.
- Eric
prev parent reply other threads:[~2020-01-03 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 20:43 [PATCH] fscrypt: move fscrypt_d_revalidate() to fname.c Eric Biggers
2020-01-03 16:59 ` Eric Biggers [this message]
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=20200103165938.GG19521@gmail.com \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@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).