From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mike Marshall <hubcap@omnibond•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Martin Brandenburg <martin@omnibond•com>
Subject: linux-next: build failure after merge of the orangefs tree
Date: Thu, 11 Apr 2019 09:19:47 +1000 [thread overview]
Message-ID: <20190411091947.741fa90d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hi Mike,
After merging the orangefs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/home/sfr/next/next/fs/orangefs/file.c:438:18: error: initialization of 'vm_fault_t (*)(struct vm_fault *)' {aka 'unsigned int (*)(struct vm_fault *)'} from incompatible pointer type 'int (*)(struct vm_fault *)' [-Werror=incompatible-pointer-types]
.page_mkwrite = orangefs_page_mkwrite,
^~~~~~~~~~~~~~~~~~~~~
Caused by commit
c32607e8fc3b ("orangefs: write range tracking")
I have used the orangefs tree from next-20190410 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2019-04-10 23:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190411091947.741fa90d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hubcap@omnibond$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin@omnibond$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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