On Tue, Jan 03, 2017 at 10:49:26AM +0100, Richard Weinberger wrote:
> Ted,
>
> Am 01.01.2017 um 22:47 schrieb Theodore Ts'o:
> > On Mon, Dec 19, 2016 at 12:25:32PM +0100, Richard Weinberger wrote:
> >> That way we can get rid of the direct dependency on CONFIG_BLOCK.
> >>
> >> Reported-by: Arnd Bergmann <arnd@xxxxxxxx>
> >> Reported-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> >> Suggested-by: Christoph Hellwig <hch@xxxxxxxxxxxxx>
> >> Fixes: d475a507457b ("ubifs: Add skeleton for fscrypto")
> >> Signed-off-by: Richard Weinberger <richard@xxxxxx>
> >
> > Applied, thanks.
>
> Just to make sure, this fixes a build error and should
> go into Linus' tree ASAP.
I didn't consider this a build error since it could be fixed via a
config change. And it is a pretty big patch, even if it is mostly
moving (not that git recognized it as such)...
git show --stat -M 58ae74683ae2c07cd717a91799edb50231061938
commit 58ae74683ae2c07cd717a91799edb50231061938
Author: Richard Weinberger <richard@xxxxxx>
Date: Mon Dec 19 12:25:32 2016 +0100
fscrypt: factor out bio specific functions
That way we can get rid of the direct dependency on CONFIG_BLOCK.
Fixes: d475a507457b ("ubifs: Add skeleton for fscrypto")
Reported-by: Arnd Bergmann <arnd@xxxxxxxx>
Reported-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Reviewed-by: Eric Biggers <ebiggers@xxxxxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>
Reviewed-by: David Gstir <david@xxxxxxxxxxxxx>
Signed-off-by: Richard Weinberger <richard@xxxxxx>
Signed-off-by: Theodore Ts'o <tytso@xxxxxxx>
fs/crypto/Kconfig | 1 -
fs/crypto/Makefile | 1 +
fs/crypto/bio.c | 145 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/crypto/crypto.c | 157 +++++++++----------------------------------------------------------------------------
fs/crypto/fscrypt_private.h | 16 ++++++++-
include/linux/fscrypto.h | 11 +++---
6 files changed, 184 insertions(+), 147 deletions(-)
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
