From: Eric Biggers <ebiggers3@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-fsdevel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] fscrypt: constify struct fscrypt_operations
Date: Thu, 5 Jan 2017 16:09:59 -0800 [thread overview]
Message-ID: <20170106000959.GA49081@gmail.com> (raw)
In-Reply-To: <ce5939bb-87b1-a011-f694-8002a0766eb7@nod.at>
On Fri, Jan 06, 2017 at 01:03:33AM +0100, Richard Weinberger wrote:
> Am 05.01.2017 um 21:42 schrieb Eric Biggers:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> > fs/ext4/super.c | 4 ++--
> > fs/f2fs/super.c | 4 ++--
> > fs/ubifs/crypto.c | 2 +-
> > fs/ubifs/super.c | 2 +-
> > fs/ubifs/ubifs.h | 2 +-
> > 5 files changed, 7 insertions(+), 7 deletions(-)
>
> Reviewed-by: Richard Weinberger <richard@nod.at>
>
> Eric, I assume you did also a build test with UBIFS enabled, right?
> Constifying stuff often looks easy but can uncover horrors. ;D
>
Yes, I compiled with ext4, f2fs, and ubifs enabled, both with and without
encryption enabled for each filesystem.
Eric
next prev parent reply other threads:[~2017-01-06 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 20:42 [PATCH] fscrypt: constify struct fscrypt_operations Eric Biggers
2017-01-06 0:03 ` Richard Weinberger
2017-01-06 0:09 ` Eric Biggers [this message]
2017-01-23 20:16 ` Eric Biggers
2017-02-07 20:42 ` [PATCH v2] " Eric Biggers
2017-02-08 16:17 ` Theodore Ts'o
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=20170106000959.GA49081@gmail.com \
--to=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=richard@nod.at \
--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 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).