From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build failure after merge of the btrfs-kdave tree
Date: Fri, 9 Feb 2018 00:48:46 +0100 [thread overview]
Message-ID: <20180208234846.GF3003@suse.cz> (raw)
In-Reply-To: <20180209104057.0e999c19@canb.auug.org.au>
On Fri, Feb 09, 2018 at 10:40:57AM +1100, Stephen Rothwell wrote:
> 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")
Right, I had fixed it in my local branch but did not push the update,
sorry. Current for-next, top commit 993b08a92e32 builds fine.
next prev parent reply other threads:[~2018-02-08 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 23:40 linux-next: build failure after merge of the btrfs-kdave tree Stephen Rothwell
2018-02-08 23:48 ` David Sterba [this message]
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=20180208234846.GF3003@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=sfr@canb.auug.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.