All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: xfs@oss.sgi.com, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: build failure after merge of the xfs tree
Date: Tue, 30 Apr 2013 13:36:47 -0500	[thread overview]
Message-ID: <20130430183647.GF812@sgi.com> (raw)
In-Reply-To: <20130429014002.GY10481@dastard>

Hey Stephen and Dave,

On Mon, Apr 29, 2013 at 11:40:02AM +1000, Dave Chinner wrote:
> On Mon, Apr 29, 2013 at 11:29:43AM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the xfs tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > ERROR: "xfs_dquot_buf_ops" [fs/xfs/xfs.ko] undefined!
> > 
> > Probably caused by commit 3fe58f30b4fc ("xfs: add CRC checks for quota
> > blocks").
> > 
> > I have used the xfs tree from next-20130426 for today.
> 
> CONFIG_XFS_QUOTA=y will fix it.
> 
> Or, alternatively, apply this patch:
> 
> http://oss.sgi.com/pipermail/xfs/2013-April/025434.html

I applied this patch so it should be fixed today.

Regards,
	Ben

WARNING: multiple messages have this Message-ID (diff)
From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: linux-next: build failure after merge of the xfs tree
Date: Tue, 30 Apr 2013 13:36:47 -0500	[thread overview]
Message-ID: <20130430183647.GF812@sgi.com> (raw)
In-Reply-To: <20130429014002.GY10481@dastard>

Hey Stephen and Dave,

On Mon, Apr 29, 2013 at 11:40:02AM +1000, Dave Chinner wrote:
> On Mon, Apr 29, 2013 at 11:29:43AM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the xfs tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > ERROR: "xfs_dquot_buf_ops" [fs/xfs/xfs.ko] undefined!
> > 
> > Probably caused by commit 3fe58f30b4fc ("xfs: add CRC checks for quota
> > blocks").
> > 
> > I have used the xfs tree from next-20130426 for today.
> 
> CONFIG_XFS_QUOTA=y will fix it.
> 
> Or, alternatively, apply this patch:
> 
> http://oss.sgi.com/pipermail/xfs/2013-April/025434.html

I applied this patch so it should be fixed today.

Regards,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-04-30 18:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29  1:29 linux-next: build failure after merge of the xfs tree Stephen Rothwell
2013-04-29  1:29 ` Stephen Rothwell
2013-04-29  1:40 ` Dave Chinner
2013-04-29  1:40   ` Dave Chinner
2013-04-30 18:36   ` Ben Myers [this message]
2013-04-30 18:36     ` Ben Myers
  -- strict thread matches above, loose matches on Subject: below --
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
2016-02-09  0:17 Stephen Rothwell
2016-02-09  0:17 ` Stephen Rothwell
2016-02-09  0:30 ` Eric Sandeen
2016-02-09  0:30   ` Eric Sandeen
2016-02-09  0:41   ` Stephen Rothwell
2016-02-09  0:41     ` Stephen Rothwell
2015-04-20  2:35 Stephen Rothwell
2015-04-20  2:35 ` Stephen Rothwell
2012-05-10  3:01 Stephen Rothwell
2012-05-10  3:01 ` Stephen Rothwell
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:32   ` Ben Myers
2012-05-10 18:36   ` Mark Tinguely
2012-05-10 18:36     ` Mark Tinguely
2012-05-10 18:43     ` Ben Myers
2012-05-10 18:43       ` Ben Myers
2010-10-08  0:08 Stephen Rothwell
2010-07-26  1:51 Stephen Rothwell
2010-07-26  3:54 ` Dave Chinner
2010-07-26  4:28   ` 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=20130430183647.GF812@sgi.com \
    --to=bpm@sgi.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --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 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.