From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the btrfs tree
Date: Fri, 21 Aug 2015 10:42:10 +1000 [thread overview]
Message-ID: <20150821104210.19795868@canb.auug.org.au> (raw)
Hi all,
After merging the btrfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/btrfs/extent_io.c: In function 'btrfs_bio_clone':
fs/btrfs/extent_io.c:2734:10: error: 'struct bio' has no member named 'bi_css'
if (bio->bi_css)
^
fs/btrfs/extent_io.c:2735:32: error: 'struct bio' has no member named 'bi_css'
bio_associate_blkcg(new, bio->bi_css);
^
fs/btrfs/volumes.c: In function 'breakup_stripe_bio':
fs/btrfs/volumes.c:5958:15: error: 'struct bio' has no member named 'bi_ioc'
if (first_bio->bi_ioc) {
^
fs/btrfs/volumes.c:5959:34: error: 'struct bio' has no member named 'bi_ioc'
get_io_context_active(first_bio->bi_ioc);
^
fs/btrfs/volumes.c:5960:6: error: 'struct bio' has no member named 'bi_ioc'
bio->bi_ioc = first_bio->bi_ioc;
^
fs/btrfs/volumes.c:5960:26: error: 'struct bio' has no member named 'bi_ioc'
bio->bi_ioc = first_bio->bi_ioc;
^
fs/btrfs/volumes.c:5962:15: error: 'struct bio' has no member named 'bi_css'
if (first_bio->bi_css) {
^
fs/btrfs/volumes.c:5963:20: error: 'struct bio' has no member named 'bi_css'
css_get(first_bio->bi_css);
^
fs/btrfs/volumes.c:5964:6: error: 'struct bio' has no member named 'bi_css'
bio->bi_css = first_bio->bi_css;
^
fs/btrfs/volumes.c:5964:26: error: 'struct bio' has no member named 'bi_css'
bio->bi_css = first_bio->bi_css;
^
Caused by commit
da2f0f74cf7d ("Btrfs: add support for blkio controllers")
This build does ont have CONFIG_BLK_CGROUP set.
I have used the btrfs tree from next-20150820 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
next reply other threads:[~2015-08-21 0:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 0:42 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-12 23:36 linux-next: build failure after merge of the btrfs tree Stephen Rothwell
2023-01-13 10:59 ` David Sterba
2022-11-07 22:42 Stephen Rothwell
2022-11-08 11:21 ` David Sterba
2022-09-06 19:44 Stephen Rothwell
2022-08-21 23:44 Stephen Rothwell
2021-10-27 10:09 Stephen Rothwell
2021-10-29 8:28 ` Stephen Rothwell
2021-10-29 9:52 ` David Sterba
2021-10-29 10:50 ` David Sterba
[not found] ` <CAHp75VdXJEuY86pFC+bLoGbAYuGsA+KqEV-g4Dca25HHD-njHA@mail.gmail.com>
2021-10-29 12:14 ` David Sterba
2021-10-31 4:30 ` Stephen Rothwell
2021-10-08 4:03 Stephen Rothwell
2021-10-08 5:56 ` Qu Wenruo
2020-04-21 0:25 Stephen Rothwell
2020-04-21 0:40 ` Qu Wenruo
2020-04-21 1:13 ` Stephen Rothwell
2020-04-21 1:33 ` Qu Wenruo
2020-04-21 1:55 ` Stephen Rothwell
2020-04-22 21:29 ` David Sterba
2020-04-24 5:17 ` Qu Wenruo
2020-02-19 22:23 Stephen Rothwell
2020-02-21 11:30 ` David Sterba
2020-02-21 11:33 ` David Sterba
2012-12-16 23:00 Stephen Rothwell
2012-12-17 0:15 ` Chris Mason
2012-12-17 2:52 ` Chris Mason
2012-12-17 3:13 ` Stephen Rothwell
2012-12-17 3:38 ` Chris Mason
2012-12-17 2:01 ` Chris Mason
2012-10-01 4:22 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=20150821104210.19795868@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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.