From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chris Mason <clm@fb.com>,
Josef Bacik <jbacik@fb.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yufen Yu <yuyufen@huawei.com>, Tejun Heo <tj@kernel.org>
Subject: linux-next: build failure after merge of the f2fs tree
Date: Thu, 18 Jan 2018 10:04:30 +1100 [thread overview]
Message-ID: <20180118100430.4fc0151e@canb.auug.org.au> (raw)
Hi Jaegeuk,
After merging the f2fs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_fill_super':
/home/sfr/next/next/fs/f2fs/super.c:2563:18: error: 'SB_I_CGROUPWB' undeclared (first use in this function); did you mean 'S_CGROUPWB'?
sb->s_iflags |= SB_I_CGROUPWB;
^~~~~~~~~~~~~
S_CGROUPWB
Caused by commit
578c647879f7 ("f2fs: implement cgroup writeback support")
interacting with commit
34934189a3dd ("cgroup, writeback: replace SB_I_CGROUPWB with per-inode S_CGROUPWB"
from the btrfs tree.
I have reverted the f2fs tree commit for today, but a better resolution
would be appreciated.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2018-01-17 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 23:04 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-23 1:11 linux-next: build failure after merge of the f2fs tree Stephen Rothwell
2021-08-27 0:28 ` Stephen Rothwell
2021-06-23 0:49 Stephen Rothwell
2021-07-11 3:08 ` Stephen Rothwell
2020-11-03 1:31 Stephen Rothwell
2020-11-03 1:35 ` Jaegeuk Kim
2019-05-02 0:53 Stephen Rothwell
2019-05-02 3:42 ` Jaegeuk Kim
2014-11-05 0:58 Stephen Rothwell
2013-08-27 1:41 Stephen Rothwell
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=20180118100430.4fc0151e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=clm@fb.com \
--cc=jaegeuk@kernel.org \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yuyufen@huawei.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).