From: Richard Weinberger <richard@nod.at>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Artem Bityutskiy <dedekind1@gmail.com>,
linux-mtd@lists.infradead.org, Eric Biggers <ebiggers@google.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 15 (fs/ubifs/ causes problems in fs/crypto/)
Date: Thu, 15 Dec 2016 23:46:02 +0100 [thread overview]
Message-ID: <ac59de6f-eaac-d088-a9d7-ce77e10f8a51@nod.at> (raw)
In-Reply-To: <a29553a3-c355-43ed-7d50-3aeb7eb8b3b1@infradead.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
prev parent reply other threads:[~2016-12-15 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 3:21 linux-next: Tree for Dec 15 Stephen Rothwell
2016-12-15 18:13 ` linux-next: Tree for Dec 15 (fs/ubifs/ causes problems in fs/crypto/) Randy Dunlap
2016-12-15 22:46 ` Richard Weinberger [this message]
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=ac59de6f-eaac-d088-a9d7-ce77e10f8a51@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=ebiggers@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--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).