From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756609AbcLOWqK (ORCPT ); Thu, 15 Dec 2016 17:46:10 -0500 Received: from b.ns.miles-group.at ([95.130.255.144]:44725 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753962AbcLOWqI (ORCPT ); Thu, 15 Dec 2016 17:46:08 -0500 Subject: Re: linux-next: Tree for Dec 15 (fs/ubifs/ causes problems in fs/crypto/) To: Randy Dunlap , Stephen Rothwell , linux-next@vger.kernel.org References: <20161215142108.0ec084b0@canb.auug.org.au> Cc: linux-kernel@vger.kernel.org, Artem Bityutskiy , linux-mtd@lists.infradead.org, Eric Biggers , "Theodore Ts'o" , Ext4 Developers List From: Richard Weinberger Message-ID: Date: Thu, 15 Dec 2016 23:46:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Randy, On 15.12.2016 19:13, Randy Dunlap wrote: > On 12/14/16 19:21, Stephen Rothwell wrote: >> Hi all, >> >> Please do not add any material for v4.11 to your linux-next included >> branches until after v4.10-rc1 has been released. >> >> Changes since 20161214: >> > > on x86_64: > > when CONFIG_BLOCK is not enabled: > > warning: (UBIFS_FS_ENCRYPTION) selects FS_ENCRYPTION which has unmet direct dependencies (BLOCK) UBIFS does not depend on CONFIG_BLOCK but fs/crypto/ does. As short-term solution we can make UBIFS_FS_ENCRYPTION depend on CONFIG_BLOCK, a better solution would be extracting all block specific stuff from fs/crypto/crypto.c to another file. Thanks, //richard