From: Eric Sandeen <sandeen@sandeen.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Ben Myers <bpm@sgi.com>,
David Chinner <david@fromorbit.com>,
xfs@oss.sgi.com
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the xfs tree
Date: Mon, 8 Feb 2016 18:30:40 -0600 [thread overview]
Message-ID: <56B93330.20608@sandeen.net> (raw)
In-Reply-To: <20160209111721.359f8558@canb.auug.org.au>
Dave just sent a patch to the xfs list to fix this,
[PATCH] xfs: log recovery needs to be aware of CONFIG_XFS_RT now
Thanks,
-Eric
On 2/8/16 6:17 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the xfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> ERROR: "xfs_rtbuf_ops" [fs/xfs/xfs.ko] undefined!
>
> Caused by commit
>
> ca4de5c7e86a ("xfs: RT bitmap and summary buffers need verifiers")
>
> CONFIG_XFS_RT is not set for this build.
>
> I have used the xfs tree from next-20160208 for today.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-09 0:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 0:17 linux-next: build failure after merge of the xfs tree Stephen Rothwell
2016-02-09 0:30 ` Eric Sandeen [this message]
2016-02-09 0:41 ` Stephen Rothwell
[not found] <jZld0KWAlgFM0KGNf6_lm-4ZXRf4uFdfuPXGopJi8jUD3StPMObAqCIaJUvNZvyoyxrWEJus6A_a0yxRt7X0Eg==@protonmail.internalid>
2025-07-18 0:08 ` Stephen Rothwell
2025-07-18 8:30 ` Carlos Maiolino
2025-07-18 8:33 ` Christoph Hellwig
2025-07-18 8:45 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 22:04 Stephen Rothwell
2024-12-11 9:44 ` Carlos Maiolino
2024-12-11 21:41 ` Carlos Maiolino
2020-07-07 0:27 Stephen Rothwell
2019-10-28 23:11 Stephen Rothwell
2019-10-28 23:18 ` Darrick J. Wong
2019-10-29 5:56 ` Christoph Hellwig
2019-10-29 6:23 ` Stephen Rothwell
2019-10-29 6:32 ` Christoph Hellwig
2019-07-01 1:12 Stephen Rothwell
2015-04-20 2:35 Stephen Rothwell
2013-04-29 1:29 Stephen Rothwell
2013-04-29 1:40 ` Dave Chinner
2013-04-30 18:36 ` Ben Myers
2012-05-10 3:01 Stephen Rothwell
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:36 ` Mark Tinguely
2012-05-10 18:43 ` Ben Myers
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=56B93330.20608@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs@oss.sgi.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