From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Josef Bacik <jbacik@fb.com>, Jan Kara <jack@suse.cz>
Subject: Re: linux-next: build failure after merge of the btrfs-kdave tree
Date: Fri, 9 Sep 2016 13:11:05 +0200 [thread overview]
Message-ID: <20160909111105.GR16983@suse.cz> (raw)
In-Reply-To: <20160907112253.3bd54c49@canb.auug.org.au>
On Wed, Sep 07, 2016 at 11:22:53AM +1000, Stephen Rothwell wrote:
> Hi David,
>
> After merging the btrfs-kdave tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/ntfs/attrib.c: In function 'ntfs_attr_set':
> fs/ntfs/attrib.c:2549:35: error: implicit declaration of function 'inode_to_bdi' [-Werror=implicit-function-declaration]
> balance_dirty_pages_ratelimited(inode_to_bdi(inode),
> ^
> fs/ntfs/attrib.c:2549:35: warning: passing argument 1 of 'balance_dirty_pages_ratelimited' makes pointer from integer without a cast [-Wint-conversion]
> In file included from include/linux/memcontrol.h:30:0,
> from include/linux/swap.h:8,
> from fs/ntfs/attrib.c:26:
> include/linux/writeback.h:367:6: note: expected 'struct backing_dev_info *' but argument is of type 'int'
> void balance_dirty_pages_ratelimited(struct backing_dev_info *bdi,
> ^
> fs/ntfs/attrib.c:2591:35: warning: passing argument 1 of 'balance_dirty_pages_ratelimited' makes pointer from integer without a cast [-Wint-conversion]
> balance_dirty_pages_ratelimited(inode_to_bdi(inode),
> ^
> In file included from include/linux/memcontrol.h:30:0,
> from include/linux/swap.h:8,
> from fs/ntfs/attrib.c:26:
> include/linux/writeback.h:367:6: note: expected 'struct backing_dev_info *' but argument is of type 'int'
> void balance_dirty_pages_ratelimited(struct backing_dev_info *bdi,
> ^
> fs/ntfs/attrib.c:2609:35: warning: passing argument 1 of 'balance_dirty_pages_ratelimited' makes pointer from integer without a cast [-Wint-conversion]
> balance_dirty_pages_ratelimited(inode_to_bdi(inode),
> ^
> In file included from include/linux/memcontrol.h:30:0,
> from include/linux/swap.h:8,
> from fs/ntfs/attrib.c:26:
> include/linux/writeback.h:367:6: note: expected 'struct backing_dev_info *' but argument is of type 'int'
> void balance_dirty_pages_ratelimited(struct backing_dev_info *bdi,
> ^
>
> Caused by commit
>
> a685fa61566d ("remove mapping from balance_dirty_pages*()")
>
> I assume some forgotten include(s).
No, I picked a wrong version of the patchset. But the patchset should
not have been in for-next as it's a change to writeback (a prerequisity
for a btrfs patchset). Now removed.
next prev parent reply other threads:[~2016-09-09 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 1:22 linux-next: build failure after merge of the btrfs-kdave tree Stephen Rothwell
2016-09-09 11:11 ` David Sterba [this message]
-- 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
2018-02-08 23:40 Stephen Rothwell
2018-02-08 23:48 ` David Sterba
2018-02-09 0:27 ` Stephen Rothwell
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=20160909111105.GR16983@suse.cz \
--to=dsterba@suse.cz \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).