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>
Subject: Re: linux-next: build failure after merge of the btrfs-kdave tree
Date: Thu, 28 Jun 2018 18:11:03 +0200 [thread overview]
Message-ID: <20180628161102.GJ2287@suse.cz> (raw)
In-Reply-To: <20180627085936.4f9cc4f2@canb.auug.org.au>
On Wed, Jun 27, 2018 at 08:59:36AM +1000, Stephen Rothwell wrote:
> After merging the btrfs-kdave tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/btrfs/print-tree.c: In function 'print_extent_item':
> fs/btrfs/print-tree.c:56:3: error: implicit declaration of function 'btrfs_print_v0_err'; did you mean 'btrfs_print_tree'? [-Werror=implicit-function-declaration]
> btrfs_print_v0_err(eb->fs_info);
> ^~~~~~~~~~~~~~~~~~
> btrfs_print_tree
Should be fixed in today's branch.
next prev parent reply other threads:[~2018-06-28 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 22:59 linux-next: build failure after merge of the btrfs-kdave tree Stephen Rothwell
2018-06-28 16:11 ` David Sterba [this message]
2018-06-28 23:58 ` Stephen Rothwell
2018-06-29 11:19 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2018-02-08 23:40 Stephen Rothwell
2018-02-08 23:48 ` David Sterba
2018-02-09 0:27 ` Stephen Rothwell
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=20180628161102.GJ2287@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 \
/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.