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: Fri, 29 Jun 2018 13:19:31 +0200 [thread overview]
Message-ID: <20180629111931.GN2287@suse.cz> (raw)
In-Reply-To: <20180629095858.655ae88f@canb.auug.org.au>
On Fri, Jun 29, 2018 at 09:58:58AM +1000, Stephen Rothwell wrote:
> Hi David,
>
> On Thu, 28 Jun 2018 18:11:03 +0200 David Sterba <dsterba@suse.cz> wrote:
> >
> > 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.
>
> Sorry, still broken. I fetched your tree only about 5 minutes ago.
It was a build problem that I did not recognize in my setup
immediatelly, the warning appears only withtout CONFIG_BTRFS_ASSERT.
The branch has been updated, commit 1607c1cbdaa0b6b80b0d4a, sorry for
inconvenience.
next prev parent reply other threads:[~2018-06-29 11:19 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
2018-06-28 23:58 ` Stephen Rothwell
2018-06-29 11:19 ` David Sterba [this message]
-- 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=20180629111931.GN2287@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 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).