From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@mellanox•com>
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 hmm tree
Date: Thu, 14 Nov 2019 16:34:35 +1100 [thread overview]
Message-ID: <20191114163435.6273b6a1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
Hi all,
After merging the hmm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/infiniband/hw/hfi1/user_exp_rcv.c: In function 'set_rcvarray_entry':
drivers/infiniband/hw/hfi1/user_exp_rcv.c:768:33: warning: passing argument 2 of 'mmu_interval_notifier_insert' makes pointer from integer without a cast [-Wint-conversion]
768 | &node->notifier, tbuf->vaddr + (pageidx * PAGE_SIZE),
| ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
| |
| long unsigned int
In file included from include/rdma/ib_verbs.h:59,
from include/rdma/ib_hdrs.h:53,
from drivers/infiniband/hw/hfi1/hfi.h:68,
from drivers/infiniband/hw/hfi1/mmu_rb.h:50,
from drivers/infiniband/hw/hfi1/user_exp_rcv.c:50:
include/linux/mmu_notifier.h:295:24: note: expected 'struct mm_struct *' but argument is of type 'long unsigned int'
295 | struct mm_struct *mm, unsigned long start,
| ~~~~~~~~~~~~~~~~~~^~
drivers/infiniband/hw/hfi1/user_exp_rcv.c:769:26: warning: passing argument 4 of 'mmu_interval_notifier_insert' makes integer from pointer without a cast [-Wint-conversion]
769 | npages * PAGE_SIZE, fd->mm);
| ~~^~~~
| |
| struct mm_struct *
In file included from include/rdma/ib_verbs.h:59,
from include/rdma/ib_hdrs.h:53,
from drivers/infiniband/hw/hfi1/hfi.h:68,
from drivers/infiniband/hw/hfi1/mmu_rb.h:50,
from drivers/infiniband/hw/hfi1/user_exp_rcv.c:50:
include/linux/mmu_notifier.h:296:20: note: expected 'long unsigned int' but argument is of type 'struct mm_struct *'
296 | unsigned long length,
| ~~~~~~~~~~~~~~^~~~~~
drivers/infiniband/hw/hfi1/user_exp_rcv.c:767:9: error: too few arguments to function 'mmu_interval_notifier_insert'
767 | ret = mmu_interval_notifier_insert(
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/rdma/ib_verbs.h:59,
from include/rdma/ib_hdrs.h:53,
from drivers/infiniband/hw/hfi1/hfi.h:68,
from drivers/infiniband/hw/hfi1/mmu_rb.h:50,
from drivers/infiniband/hw/hfi1/user_exp_rcv.c:50:
include/linux/mmu_notifier.h:294:5: note: declared here
294 | int mmu_interval_notifier_insert(struct mmu_interval_notifier *mni,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
c90dad714405 ("RDMA/hfi1: Use mmu_interval_notifier_insert for user_exp_rcv")
I have used the hmm tree from next-20191113 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-11-14 5:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 5:34 Stephen Rothwell [this message]
2019-11-14 12:58 ` linux-next: build failure after merge of the hmm tree Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 7:50 Stephen Rothwell
2021-08-23 17:33 ` Jason Gunthorpe
2021-09-01 22:01 ` Stephen Rothwell
2020-10-06 9:35 Stephen Rothwell
2020-10-06 16:41 ` Jason Gunthorpe
2020-10-12 4:19 ` Stephen Rothwell
2020-10-15 21:11 ` Stephen Rothwell
2019-09-02 10:50 Stephen Rothwell
2019-09-02 10:51 ` Jason Gunthorpe
2019-09-02 23:45 ` Stephen Rothwell
2019-09-03 5:31 ` Dan Williams
2019-09-03 5:42 ` Stephen Rothwell
2019-09-03 23:11 ` Dan Williams
2019-07-01 11:33 Stephen Rothwell
2019-07-01 23:10 ` Jason Gunthorpe
2019-07-03 1:28 ` Alex Deucher
2019-07-01 11:08 Stephen Rothwell
2019-07-09 0:21 ` Stephen Rothwell
2019-07-09 12:32 ` Jason Gunthorpe
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=20191114163435.6273b6a1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jgg@mellanox$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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