[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191224223852.GA178036@zzz.localdomain>
Date: Tue, 24 Dec 2019 16:38:52 -0600
From: Eric Biggers <ebiggers@...nel.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Theodore Y. Ts'o" <tytso@....edu>,
Jaegeuk Kim <jaegeuk@...nel.org>,
Chandan Rajendra <chandan@...ux.vnet.ibm.com>,
linux-fscrypt@...r.kernel.org
Subject: Re: [v3 PATCH] fscrypt: Allow modular crypto algorithms
On Mon, Dec 23, 2019 at 03:46:23PM +0800, Herbert Xu wrote:
> diff --git a/fs/ext4/Kconfig b/fs/ext4/Kconfig
> index ef42ab040905..930793456d3a 100644
> --- a/fs/ext4/Kconfig
> +++ b/fs/ext4/Kconfig
> @@ -10,6 +10,7 @@ config EXT3_FS
> select CRC16
> select CRYPTO
> select CRYPTO_CRC32C
> + select FS_ENCRYPTION_ALGS if FS_ENCRYPTION
> help
> This config option is here only for backward compatibility. ext3
> filesystem is now handled by the ext4 driver.
This needs to be under EXT4_FS, not EXT3_FS. That should address the kbuild
test robot error.
(The fact that EXT3_FS selects options other than just EXT4_FS is unnecessary
and misleading; I'll send a separate patch to clean that up.)
- Eric
Powered by blists - more mailing lists