Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*linux\-next\:\s+build\s+failure\s+after\s+merge\s+of\s+the\s+xfs\s+tree\s*$/: 11 ]

Total 11 documents matching your query.

1. linux-next: build failure after merge of the xfs tree (score: 1)
Author: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Thu, 10 May 2012 13:01:34 +1000
Hi all, After merging the xfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: ERROR: ".xfs_extent_busy_trim" [fs/xfs/xfs.ko] undefined! Caused by commit e459df5b5b93 ("xfs:
/archives/xfs/2012-05/msg00129.html (7,026 bytes)

2. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Thu, 10 May 2012 13:32:45 -0500
Thanks Stephen. The following should resolve the issue. Regards, Ben xfs: make xfs_extent_busy_trim not static Commit e459df5, 'xfs: move busy extent handling to it's own file' moved some code from x
/archives/xfs/2012-05/msg00135.html (10,619 bytes)

3. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Mark Tinguely <tinguely@xxxxxxx>
Date: Thu, 10 May 2012 13:36:14 -0500
Signed-off-by: Ben Myers<bpm@xxxxxxx> Index: xfs/fs/xfs/xfs_alloc.c == -- xfs.orig/fs/xfs/xfs_alloc.c +++ xfs/fs/xfs/xfs_alloc.c @@ -47,8 +47,6 @@ STATIC int xfs_alloc_ag_vextent_near(xfs STATIC int
/archives/xfs/2012-05/msg00136.html (9,985 bytes)

4. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Thu, 10 May 2012 13:43:23 -0500
CONFIG_XFS_DEBUG clears the #define of STATIC. That's where this went off the rails. Thanks, Ben
/archives/xfs/2012-05/msg00137.html (10,847 bytes)

5. linux-next: build failure after merge of the xfs tree (score: 1)
Author: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Mon, 29 Apr 2013 11:29:43 +1000
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 (
/archives/xfs/2013-04/msg00628.html (7,869 bytes)

6. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 29 Apr 2013 11:40:02 +1000
CONFIG_XFS_QUOTA=y will fix it. Or, alternatively, apply this patch: http://oss.sgi.com/pipermail/xfs/2013-April/025434.html Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
/archives/xfs/2013-04/msg00629.html (8,549 bytes)

7. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Tue, 30 Apr 2013 13:36:47 -0500
Hey Stephen and Dave, I applied this patch so it should be fixed today. Regards, Ben
/archives/xfs/2013-04/msg00666.html (9,034 bytes)

8. linux-next: build failure after merge of the xfs tree (score: 1)
Author: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Mon, 20 Apr 2015 12:35:24 +1000
Hi all, After merging the xfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: fs/xfs/xfs_file.c: In function 'xfs_file_dio_aio_write': fs/xfs/xfs_file.c:744:8: warning: pas
/archives/xfs/2015-04/msg00207.html (9,005 bytes)

9. linux-next: build failure after merge of the xfs tree (score: 1)
Author: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Tue, 9 Feb 2016 11:17:21 +1100
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 bitm
/archives/xfs/2016-02/msg00246.html (7,215 bytes)

10. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 8 Feb 2016 18:30:40 -0600
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
/archives/xfs/2016-02/msg00247.html (8,626 bytes)

11. Re: linux-next: build failure after merge of the xfs tree (score: 1)
Author: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Date: Tue, 9 Feb 2016 11:41:02 +1100
Hi Eric, Thanks. Hopefully it will be fixed in the xfs tree for linux-next tomorrow, then, -- Cheers, Stephen Rothwell
/archives/xfs/2016-02/msg00248.html (8,687 bytes)


This search system is powered by Namazu