Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info

2023-10-09 Thread Neal Gompa
On Sun, Oct 8, 2023 at 11:44 PM Eric Biggers wrote: > > On Sun, Oct 08, 2023 at 02:11:36AM -0400, Neal Gompa wrote: > > > > Looks reasonable to me. > > > > Reviewed-by: Neal Gompa > > > > Thanks. BTW, please only quote the part that you're replying to. > Well, I was replying to the whole patch,

Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info

2023-10-08 Thread Eric Biggers
On Sun, Oct 08, 2023 at 02:11:36AM -0400, Neal Gompa wrote: > > Looks reasonable to me. > > Reviewed-by: Neal Gompa > Thanks. BTW, please only quote the part that you're replying to. - Eric

Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info

2023-10-07 Thread Neal Gompa
On Thu, Oct 5, 2023 at 11:35 AM Eric Biggers wrote: > > From: Josef Bacik > > We are going to track per-extent information, so it'll be necessary to > distinguish between inode infos and extent infos. Rename fscrypt_info > to fscrypt_inode_info, adjusting any lines that now exceed 80 > character

[PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info

2023-10-05 Thread Eric Biggers
From: Josef Bacik We are going to track per-extent information, so it'll be necessary to distinguish between inode infos and extent infos. Rename fscrypt_info to fscrypt_inode_info, adjusting any lines that now exceed 80 characters. Signed-off-by: Josef Bacik [ebiggers: renamed fscrypt_get_inf