Linux filesystem development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
	Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH RESEND] libfs: unexport generic_ci_d_compare() and generic_ci_d_hash()
Date: Tue, 12 Jan 2021 11:14:03 -0800	[thread overview]
Message-ID: <X/30+5rc1bv39moX@sol.localdomain> (raw)
In-Reply-To: <20201228232529.45365-1-ebiggers@kernel.org>

On Mon, Dec 28, 2020 at 03:25:29PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Now that generic_set_encrypted_ci_d_ops() has been added and ext4 and
> f2fs are using it, it's no longer necessary to export
> generic_ci_d_compare() and generic_ci_d_hash() to filesystems.
> 
> Reviewed-by: Gabriel Krisman Bertazi <krisman@collabora.com>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  fs/libfs.c         | 8 +++-----
>  include/linux/fs.h | 5 -----
>  2 files changed, 3 insertions(+), 10 deletions(-)

Jaegeuk, any interest in applying this given that this code came in through the
f2fs tree in the first place?

- Eric

  reply	other threads:[~2021-01-12 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 23:25 [PATCH RESEND] libfs: unexport generic_ci_d_compare() and generic_ci_d_hash() Eric Biggers
2021-01-12 19:14 ` Eric Biggers [this message]
2021-01-12 22:26   ` Jaegeuk Kim

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=X/30+5rc1bv39moX@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=krisman@collabora.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@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