[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160403074505.GG3334@thunk.org>
Date: Sun, 3 Apr 2016 03:45:05 -0400
From: Theodore Ts'o <tytso@....edu>
To: Eric Biggers <ebiggers3@...il.com>
Cc: linux-fsdevel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, jaegeuk@...nel.org,
mhalcrow@...gle.com
Subject: Re: [PATCH 02/13] fscrypto: rename some functions for clarity
On Sun, Apr 03, 2016 at 12:21:53AM -0500, Eric Biggers wrote:
> Rename fscrypt_complete() to page_crypt_complete(). This callback is
> specifically for data pages; fscrypto also performs filename encryption.
>
> Rename dir_crypt_complete() to fname_crypt_complete(). This callback is
> also used for symlink targets, not just directory entries.
>
> Rename fscrypt_process_policy() to fscrypt_set_policy(). The new name
> better matches the ioctl, and it goes along with fscrypt_get_policy().
>
> Signed-off-by: Eric Biggers <ebiggers3@...il.com>
I'd really rather not renaming any globally visible functions until
after ext4 is converted over to use fs/crypto, just to avoid confusion.
Cheers,
- Ted
Powered by blists - more mailing lists