[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230119083301.5shri6z3y4eivcpy@wittgenstein>
Date: Thu, 19 Jan 2023 09:33:01 +0100
From: Christian Brauner <brauner@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christian Brauner <christian@...uner.io>,
Seth Forshee <sforshee@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the vfs-idmapping tree
On Thu, Jan 19, 2023 at 10:26:59AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the vfs-idmapping tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_setattr':
> arch/powerpc/platforms/cell/spufs/inode.c:103:22: error: passing argument 1 of 'setattr_copy' from incompatible pointer type [-Werror=incompatible-pointer-types]
> 103 | setattr_copy(&idmap, inode, attr);
> | ^~~~~~
> | |
> | struct mnt_idmap **
> In file included from arch/powerpc/platforms/cell/spufs/inode.c:12:
> include/linux/fs.h:2941:19: note: expected 'struct mnt_idmap *' but argument is of type 'struct mnt_idmap **'
> 2941 | void setattr_copy(struct mnt_idmap *, struct inode *inode,
> | ^~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
Ah, cross-compilation...
Thanks for catching and reporting this, Steven!
Fixed now and pushed out.
Christian
Powered by blists - more mailing lists