From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the xfs tree
Date: Mon, 1 Jul 2019 11:12:09 +1000 [thread overview]
Message-ID: <20190701111209.699082b7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Hi all,
After merging the xfs tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
fs/orangefs/file.c: In function 'orangefs_getflags':
fs/orangefs/file.c:372:7: warning: assignment to 'long unsigned int *' from '__u64' {aka 'long long unsigned int'} makes pointer from integer without a cast [-Wint-conversion]
uval = val;
^
fs/orangefs/file.c: In function 'orangefs_ioctl':
fs/orangefs/file.c:381:24: error: implicit declaration of function 'file_ioctl'; did you mean 'file_path'? [-Werror=implicit-function-declaration]
struct inode *inode = file_ioctl(file);
^~~~~~~~~~
file_path
fs/orangefs/file.c:381:24: warning: initialization of 'struct inode *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
fs/orangefs/file.c:418:35: error: 'old_uval' undeclared (first use in this function); did you mean 'p4d_val'?
ret = orangefs_getflags(inode, &old_uval);
^~~~~~~~
p4d_val
fs/orangefs/file.c:418:35: note: each undeclared identifier is reported only once for each function it appears in
Caused by commit
de2baa49bbae ("vfs: create a generic checking and prep function for FS_IOC_SETFLAGS")
I have used the xfs tree from next-20190628 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-07-01 1:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 1:12 Stephen Rothwell [this message]
[not found] <jZld0KWAlgFM0KGNf6_lm-4ZXRf4uFdfuPXGopJi8jUD3StPMObAqCIaJUvNZvyoyxrWEJus6A_a0yxRt7X0Eg==@protonmail.internalid>
2025-07-18 0:08 ` linux-next: build failure after merge of the xfs tree Stephen Rothwell
2025-07-18 8:30 ` Carlos Maiolino
2025-07-18 8:33 ` Christoph Hellwig
2025-07-18 8:45 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 22:04 Stephen Rothwell
2024-12-11 9:44 ` Carlos Maiolino
2024-12-11 21:41 ` Carlos Maiolino
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
2016-02-09 0:17 Stephen Rothwell
2016-02-09 0:30 ` Eric Sandeen
2016-02-09 0:41 ` Stephen Rothwell
2015-04-20 2:35 Stephen Rothwell
2013-04-29 1:29 Stephen Rothwell
2013-04-29 1:40 ` Dave Chinner
2013-04-30 18:36 ` Ben Myers
2012-05-10 3:01 Stephen Rothwell
2012-05-10 18:32 ` Ben Myers
2012-05-10 18:36 ` Mark Tinguely
2012-05-10 18:43 ` Ben Myers
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=20190701111209.699082b7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.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