From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <christian@brauner.io>,
Seth Forshee <sforshee@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the vfs-idmapping tree
Date: Thu, 19 Jan 2023 10:26:59 +1100 [thread overview]
Message-ID: <20230119102659.5f7d3b39@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
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
Caused by commit
2e906ff8067f ("fs: port ->setattr() to pass mnt_idmap")
I have used the vfs-idmapping tree from next-20230118 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-18 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 23:26 Stephen Rothwell [this message]
2023-01-19 8:33 ` linux-next: build failure after merge of the vfs-idmapping tree Christian Brauner
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=20230119102659.5f7d3b39@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sforshee@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).