From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>
Subject: linux-next: build failure after merge of the btrfs-kdave tree
Date: Fri, 9 Feb 2018 10:40:57 +1100 [thread overview]
Message-ID: <20180209104057.0e999c19@canb.auug.org.au> (raw)
Hi David,
[Seems I somehow failed to actually send the following message a couple
of days ago, sorry.]
After merging the btrfs-kdave tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/btrfs/tree-checker.c:33:10: fatal error: hash.h: No such file or directory
#include "hash.h"
^~~~~~~~
Caused by commit
8bd2a9b19fd7 ("btrfs: Remove custom crc32c init code")
interacting with commit
ad7b0368f33c ("btrfs: tree-checker: Add checker for dir item")
from Linus' tree.
It should have been fixed up in commit
99ca8d38ea90 ("Merge branch 'ext/nikbor/libcrc32c' into for-next-next-v4.16-20180206")
I have used the btrfs-kdave tree from next-20180206 for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2018-02-08 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 23:40 Stephen Rothwell [this message]
2018-02-08 23:48 ` linux-next: build failure after merge of the btrfs-kdave tree David Sterba
2018-02-09 0:27 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 22:59 Stephen Rothwell
2018-06-28 16:11 ` David Sterba
2018-06-28 23:58 ` Stephen Rothwell
2018-06-29 11:19 ` David Sterba
2016-09-07 1:22 Stephen Rothwell
2016-09-09 11:11 ` David Sterba
2016-02-01 23:39 Stephen Rothwell
2016-02-02 8:54 ` David Sterba
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=20180209104057.0e999c19@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=wqu@suse.com \
/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).