Re: linux-next: build failure after merge of the vfs tree

On Tue, Jan 05, 2021 at 09:36:16AM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from arch/x86/include/asm/elf.h:8, > from include/linux/elf.h:6, >

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Tue, 10 Nov 2020 19:00:36 + Al Viro wrote: > > On Tue, Oct 27, 2020 at 04:59:12AM +, Al Viro wrote: > > > I'll rebase that branch on top of sparc tree tomorrow (and eventually I'd > > like > > it to go through the sparc tree anyway). > > Done - sorry for disappearing ;-/ N

Re: linux-next: build failure after merge of the vfs tree

On Tue, Oct 27, 2020 at 04:59:12AM +, Al Viro wrote: > I'll rebase that branch on top of sparc tree tomorrow (and eventually I'd like > it to go through the sparc tree anyway). Done - sorry for disappearing ;-/

Re: linux-next: build failure after merge of the vfs tree

On Tue, Oct 27, 2020 at 03:14:14PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (sparc_defconfig) > failed like this: > > arch/sparc/lib/memset.S: Assembler messages: > arch/sparc/lib/memset.S:149: Error: Unknown opcode: `ext(12b, 13b,21f)' >

Re: linux-next: build failure after merge of the vfs tree

On Wed, Oct 07, 2020 at 08:04:05AM +1100, Stephen Rothwell wrote: > Hi Josh, > > On Tue, 6 Oct 2020 09:30:12 -0500 Josh Poimboeuf wrote: > > > > On Mon, Sep 28, 2020 at 11:10:56PM -0500, Josh Poimboeuf wrote: > > > > Josh, any ideas? We could, of course, make it "r"(size), but that would > > > >

Re: linux-next: build failure after merge of the vfs tree

Hi Josh, On Tue, 6 Oct 2020 09:30:12 -0500 Josh Poimboeuf wrote: > > On Mon, Sep 28, 2020 at 11:10:56PM -0500, Josh Poimboeuf wrote: > > > Josh, any ideas? We could, of course, make it "r"(size), but that would > > > be unpleasant in all existing callers... > > > > Sorry, I've been traveling.

Re: linux-next: build failure after merge of the vfs tree

On Mon, Sep 28, 2020 at 11:10:56PM -0500, Josh Poimboeuf wrote: > > Josh, any ideas? We could, of course, make it "r"(size), but that would > > be unpleasant in all existing callers... > > Sorry, I've been traveling. I'd just vote for making it "r". > > array_index_nospec() is always called aft

Re: linux-next: build failure after merge of the vfs tree

On Fri, Sep 25, 2020 at 02:38:20PM +0100, Al Viro wrote: > On Fri, Sep 25, 2020 at 10:01:28PM +1000, Stephen Rothwell wrote: > > $ x86_64-linux-gnu-gcc --version > > x86_64-linux-gnu-gcc (Debian 10.2.0-9) 10.2.0 > > $ x86_64-linux-gnu-ld --version > > GNU ld (GNU Binutils for Debian) 2.35 > > > >

Re: linux-next: build failure after merge of the vfs tree

That is the crude fix, and it should work. I'd much rather make compat_iovec always available, though. Let me give that a spin.

Re: linux-next: build failure after merge of the vfs tree

On Fri, Sep 25, 2020 at 10:01:28PM +1000, Stephen Rothwell wrote: > $ x86_64-linux-gnu-gcc --version > x86_64-linux-gnu-gcc (Debian 10.2.0-9) 10.2.0 > $ x86_64-linux-gnu-ld --version > GNU ld (GNU Binutils for Debian) 2.35 > > and the gcc plugins don't get built for the allnoconfig builds. > I re

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Thu, 24 Sep 2020 21:08:07 +0100 Al Viro wrote: > > On Thu, Sep 24, 2020 at 06:30:38PM +1000, Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > > failed like this: > > > > arch/x86/include/asm/barrier.h: Assembler messages: > >

Re: linux-next: build failure after merge of the vfs tree

On Thu, Sep 24, 2020 at 06:30:38PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > arch/x86/include/asm/barrier.h: Assembler messages: > arch/x86/include/asm/barrier.h:41: Error: operand type mismatch f

Re: linux-next: build failure after merge of the vfs tree

On Wed, Jul 29, 2020 at 08:33:05AM +0200, Christoph Hellwig wrote: > Thanks, > > I've sent out a fixed version. #work.quota-compat and #for-next rebuilt (and pushed) with it...

Re: linux-next: build failure after merge of the vfs tree

Thanks, I've sent out a fixed version.

Re: linux-next: build failure after merge of the vfs tree

On 5/6/20 8:35 PM, Al Viro wrote: > On Thu, May 07, 2020 at 10:39:21AM +1000, Stephen Rothwell wrote: >> Hi all, >> >> After merging the vfs tree, today's linux-next build (arm >> multi_v7_defconfig) failed like this: >> >> fs/eventfd.c: In function 'eventfd_read': >> fs/eventfd.c:226:6: error: imp

Re: linux-next: build failure after merge of the vfs tree

On Thu, May 07, 2020 at 10:39:21AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the vfs tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > fs/eventfd.c: In function 'eventfd_read': > fs/eventfd.c:226:6: error: implicit declaration of function 'iov_iter_c

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Wed, 2 Jan 2019 15:01:40 +1100 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/fs_context.c: In function 'logfc': > fs/fs_context.c:400:3: error: implicit declaration of function > 'vprintk_emit'; did y

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Mon, 29 Oct 2018 09:21:20 + David Howells wrote: > > I think these changes should cover them all. Yep, that fixes the build for me, thanks. Tested-by: Stephen Rothwell -- Cheers, Stephen Rothwell pgpUP0DRJWa3r.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the vfs tree

I think these changes should cover them all. David --- diff --git a/samples/vfs/test-fs-query.c b/samples/vfs/test-fs-query.c index 511541d12b9e..4635bf1eb3d4 100644 --- a/samples/vfs/test-fs-query.c +++ b/samples/vfs/test-fs-query.c @@ -27,6 +27,13 @@ #include #include +#ifndef __NR_fsopen

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Mon, 29 Oct 2018 15:33:34 +1100 Stephen Rothwell wrote: > > Hi Al, David, > > These have returned, so I have disabled CONFIG_SAMPLE_VFS again. Here is the current set of errors I git today (this is from a PowerPC allyesconfig build native compiler on a PowerPC64 LE machine): samp

Re: linux-next: build failure after merge of the vfs tree

Hi Al, David, These have returned, so I have disabled CONFIG_SAMPLE_VFS again. On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > s

Re: linux-next: build failure after merge of the vfs tree

Hi Jaegeuk, On Tue, 16 Oct 2018 09:37:44 -0700 Jaegeuk Kim wrote: > > I've modified this patch in f2fs tree to use SB_RDONLY. Thanks for that. -- Cheers, Stephen Rothwell pgpFgDa4GbUu9.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the vfs tree

On 10/16, Stephen Rothwell wrote: > Hi all, > > On Wed, 3 Oct 2018 10:32:22 +1000 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': > > /home

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Wed, 3 Oct 2018 10:32:22 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_remount': > /home/sfr/next/next/fs/f2fs/super.c:1589:16: error: 'MS_RDO

Re: linux-next: build failure after merge of the vfs tree

Michael Ellerman wrote: > I realise these are in samples rather than selftests, but what most of > the selftests do is just #define the syscall number if it's not defined, > so that you're not dependent on getting the headers. The reason I don't want to do that is that syscall numbers aren't con

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell writes: > Hi David, > > On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote: >> >> Stephen Rothwell wrote: >> >> > > I think the problem is that I haven't allocated system call numbers for >> > > any arches other than x86 - even the x86 syscall numbers are provisional >> > >

Re: linux-next: build failure after merge of the vfs tree

David Howells writes: > Stephen Rothwell wrote: > >> > After merging the vfs tree, today's linux-next build (powerpc >> > allyesconfig) failed like this: >> > >> > samples/vfs/test-fsinfo.c: In function 'fsinfo': >> > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first >> >

Re: linux-next: build failure after merge of the vfs tree

On Wed, Sep 19, 2018 at 1:50 AM Stephen Rothwell wrote: > On Tue, 18 Sep 2018 23:17:21 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (powerpc > > > > allyesconfig) failed like this: > > > > > > > > samples/vfs/test-fsinfo.c: I

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > I think the problem is that I haven't allocated system call numbers for > > > any arches other than x86 - even the x86 syscall numbers are provisional > > > until the patchset is taken upstream

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > > I think the problem is that I haven't allocated system call numbers for > > any arches other than x86 - even the x86 syscall numbers are provisional > > until the patchset is taken upstream. I'm not sure of the best way to > > deal with this - make the samples depende

Re: linux-next: build failure after merge of the vfs tree

Hi David, On Tue, 18 Sep 2018 23:17:21 +0100 David Howells wrote: > > Stephen Rothwell wrote: > > > > After merging the vfs tree, today's linux-next build (powerpc > > > allyesconfig) failed like this: > > > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > > samples/vfs/test-fsinfo.c

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (first use > > in this function); did you m

Re: linux-next: build failure after merge of the vfs tree

Hi David, Al, On Mon, 10 Sep 2018 13:35:25 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > samples/vfs/test-fsinfo.c: In function 'fsinfo': > samples/vfs/test-fsinfo.c:37:17: error: '__NR_fsinfo' undeclared (f

Re: linux-next: build failure after merge of the vfs tree

2018-08-07 9:59 GMT+09:00 Stephen Rothwell : > Hi all, > > On Mon, 6 Aug 2018 22:24:01 +1000 Stephen Rothwell > wrote: >> >> On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell >> wrote: >> > >> > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) >> > failed like this: >

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 6 Aug 2018 22:24:01 +1000 Stephen Rothwell wrote: > > On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > samples/statx/test-fsinfo.c:26:10: fatal error: li

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 6 Aug 2018 10:37:38 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > samples/statx/test-fsinfo.c:26:10: fatal error: linux/fsinfo.h: No such file > or directory > #include > ^~~~

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Sun, 8 Apr 2018 03:19:56 +0100 Al Viro wrote: > > > > Caused by commit > > > > > > 92afc556e622 ("buffer.c: call thaw_super during emergency thaw") > > > > > > I have reverted that commit for today. > > > > I am still doing that revert ... > > That's interesting, seeing that t

Re: linux-next: build failure after merge of the vfs tree

On Tue, Apr 03, 2018 at 12:26:29PM +1000, Stephen Rothwell wrote: > Hi Al, > > On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > > failed like this: > > > > fs/super.c: In function 'do_thaw_all_callba

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Mon, 19 Mar 2018 17:06:27 +1100 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of function > 'emergency_thaw_

Re: linux-next: build failure after merge of the vfs tree

On Mon, Mar 19, 2018 at 05:06:27PM +1100, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > fs/super.c: In function 'do_thaw_all_callback': > fs/super.c:942:3: error: implicit declaration of function > 'emergenc

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > - if (inode->i_mode & S_IALLUGO != 0775) > + if ((inode->i_mode & S_IALLUGO) != 0775) Acked-by: David Howells

Re: linux-next: build failure after merge of the vfs tree

On Mon, Jul 10, 2017 at 12:15:11PM +1000, Stephen Rothwell wrote: > Hi Al, > Caused by commit > > 4f9365d9e2e7 ("spufs: Implement show_options") Obvious incremental follows, will fold and push diff --git a/arch/powerpc/platforms/cell/spufs/inode.c b/arch/powerpc/platforms/cell/spufs/inode.c

Re: linux-next: build failure after merge of the vfs tree

Stephen Rothwell wrote: > From: Stephen Rothwell > Date: Mon, 27 Feb 2017 11:21:47 +1100 > Subject: [PATCH] statx: disable the sample code for now > > Signed-off-by: Stephen Rothwell > --- > samples/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/samples/Kconfig b/samples/Kc

Re: linux-next: build failure after merge of the vfs tree

On Fri, Jul 29, 2016 at 11:19:38AM +1000, Stephen Rothwell wrote: > --- > fs/fuse/dir.c| 2 +- > fs/fuse/fuse_i.h | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c > index f910578e51ba..c47b7780ce37 100644 > --- a/fs/fuse/dir.c > +++ b/f

Re: linux-next: build failure after merge of the vfs tree

Hi Al/Stephen - Original Message - > From: "Al Viro" > To: "Stephen Rothwell" > Cc: "Steven Whitehouse" , "Bob Peterson" > , linux-n...@vger.kernel.org, > linux-kernel@vger.kernel.org, "Abhi Das" > Sent: Sunday, M

Re: linux-next: build failure after merge of the vfs tree

On Mon, May 02, 2016 at 11:25:27AM +1000, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from include/linux/notifier.h:13:0, > from include/linux/memory_hotplug.h:6, >

Re: linux-next: build failure after merge of the vfs tree

On Thu, Jan 07, 2016 at 11:42:53AM +1100, Stephen Rothwell wrote: > > This patch now looks like this (after changes to the orangefs tree): > > Guys, just set inode->i_link to ORANGEFS_I(dentry->d_inode)->link_target and have ->get_link = simple_get_link. Killing orangefs_{follow,get}_link() ent

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 21 Dec 2015 11:23:01 +1100 Stephen Rothwell wrote: > > On Thu, 10 Dec 2015 11:18:47 +1100 Stephen Rothwell > wrote: > > > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > fs/orangefs/symlink.c:26:2: error: unknown field

Re: linux-next: build failure after merge of the vfs tree

Hi Stephen, On Thu, 10 Dec 2015 11:18:47 +1100 Stephen Rothwell wrote: > > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > fs/orangefs/symlink.c:26:2: error: unknown field 'follow_link' specified in > initializer > .follow_link =

Re: linux-next: build failure after merge of the vfs tree

> Said that, there is an unpleasant bug in that area - link_target of a live > inode can be overwritten, right under the pathname resolution walking the > old contents of that thing Figuring that out is on the list. This week I've been working on cleaning up orangefs_devreq_writev, and Martin e

Re: linux-next: build failure after merge of the vfs tree

On Thu, Dec 10, 2015 at 11:23:22AM +1100, Stephen Rothwell wrote: > [Just adding the origefs maintainer to the cc list] > > -static const char *pvfs2_follow_link(struct dentry *dentry, void **cookie) > > +static const char *pvfs2_get_link(struct dentry *dentry, struct inode > > *inode, > > +

Re: linux-next: build failure after merge of the vfs tree

[Just adding the origefs maintainer to the cc list] On Thu, 10 Dec 2015 11:18:47 +1100 Stephen Rothwell wrote: > > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > fs/orangefs/symlink.c:26:2: error: unknown field 'follow_link' specif

Re: linux-next: build failure after merge of the vfs tree

2015-12-09 23:20 GMT+01:00 Stephen Rothwell : > OK, I wrote all that and then I realised that the preferred names > (XATTR_NAME_POSIX_ACL_..) have been in Linus' tree for a long time (in > include/uapi/linux/xattr.h), so you could just change the orangefs tree > to use those already. i.e. my patch

Re: linux-next: build failure after merge of the vfs tree

Hi Mike, On Wed, 9 Dec 2015 16:30:34 -0500 Mike Marshall wrote: > > I'm having a chicken-and-egg moment here... not really ... > I think "posix acls: Remove duplicate xattr name definitions" got into > linux-next after > Linus committed Linux 4.4-rc4. Yes > Unless I merge my for-next with Li

Re: linux-next: build failure after merge of the vfs tree

Hi all... I'm having a chicken-and-egg moment here... I think "posix acls: Remove duplicate xattr name definitions" got into linux-next after Linus committed Linux 4.4-rc4. Unless I merge my for-next with Linus' tree at the current (arbitrary) point, I need to wait until I can merge with rc5 be

Re: linux-next: build failure after merge of the vfs tree

Hi all, On Mon, 11 May 2015 11:26:12 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > fs/f2fs/namei.c: In function 'f2fs_encrypted_follow_link': > fs/f2fs/namei.c:336:10: warning: passing argument 2 of 'f2fs_fol

Re: linux-next: build failure after merge of the vfs tree

On Tue, Mar 24, 2015 at 02:24:22PM +1100, Stephen Rothwell wrote: > I am still applying the above patch every day ... Might be worth folding it. Al, can you do that? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org M

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Fri, 13 Mar 2015 12:02:50 +1100 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > fs/ext4/indirect.c: In function 'ext4_ind_direct_IO': > fs/ext4/indirect.c:653:2: error: implicit declaration of function

Re: linux-next: build failure after merge of the vfs tree

On Wed, Dec 10, 2014 at 06:45:37PM +1100, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > allnoconfig) failed like this: > diff --git a/fs/nsfs.c b/fs/nsfs.c > index 0791d086804d..7d98db03c2ce 100644 > --- a/fs/nsfs.c > +++ b/fs/nsfs.c > @@ -3,

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On Tue, 22 Apr 2014 11:26:53 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > fs/nfs/direct.c: In function 'nfs_direct_read_schedule_iovec': > fs/nfs/direct.c:382:4: error: implicit declaration of fun

Re: linux-next: build failure after merge of the vfs tree

On Mon, 2013-09-09 at 12:33 +1000, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > fs/autofs4/dev-ioctl.c: In function 'find_autofs_mount': > fs/autofs4/dev-ioctl.c:193:2: error: implicit declaration of fu

Re: linux-next: build failure after merge of the vfs tree

On Mon, Jun 24, 2013 at 11:35:40AM +1000, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from arch/powerpc/xmon/xmon.c:41:0: > arch/powerpc/include/asm/spu.h:245:43: error: 'struct coredu

Re: linux-next: build failure after merge of the vfs tree

On Wed, May 01, 2013 at 12:22:27PM +1000, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > net/sunrpc/auth_gss/svcauth_gss.c: In function 'write_gssp': > net/sunrpc/auth_gss/svcauth_gss.c:1329:9: error: imp

Re: linux-next: build failure after merge of the vfs tree

Hi Al, On 2013-04-08 11:15, Stephen Rothwell wrote: After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_init': arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:2990:2: error: assignment

Re: linux-next: build failure after merge of the vfs tree

On Wed, Apr 03, 2013 at 11:22:35AM +1100, Stephen Rothwell wrote: > And many, many more. > > Caused by commit 1f4fbcb8700c ("create_proc_cpu_mask() doesn't need an > argument..."). Please build test this stuff *before* publishing it. :-( "Remember to push the fixes", actually ;-/ -- To unsubscr

Re: linux-next: build failure after merge of the vfs tree

On Tue, Apr 02, 2013 at 11:26:27AM +1100, Stephen Rothwell wrote: > Hi Al, > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > arch/powerpc/kernel/lparcfg.c:44:31: error: 'proc_ppc64_lparcfg' defined but > not used [-Werror=unused-variable]