From: Giulio Moro <g.moro@qmul.ac.uk>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: [Xenomai] too few arguments to function ‘handle_mm_fault`
Date: Mon, 15 May 2017 14:43:12 +0000 [thread overview]
Message-ID: <DB6PR0701MB24563716802B31DB4E93C0F0B5E10@DB6PR0701MB2456.eurprd07.prod.outlook.com> (raw)
The recent commit
9a865549170f82561389eaa6d4dbda6f8a46d2e1
" cobalt/arm: fixups for kernel 4.8+"
seems to have broken 4.4 kernel, see build log below:
arch/arm/xenomai/machine.c: In function ‘mach_arm_prefault’:
arch/arm/xenomai/machine.c:38:20: warning: passing argument 1 of ‘handle_mm_fault’ from incompatible pointer type [-Wincompatible-pointer-types]
handle_mm_fault(vma, addr, flags);
^
In file included from arch/arm/xenomai/machine.c:21:0:
include/linux/mm.h:1165:12: note: expected ‘struct mm_struct *’ but argument is of type ‘struct vm_area_struct *’
extern int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
^
arch/arm/xenomai/machine.c:38:25: warning: passing argument 2 of ‘handle_mm_fault’ makes pointer from integer without a cast [-Wint-conversion]
handle_mm_fault(vma, addr, flags);
^
In file included from arch/arm/xenomai/machine.c:21:0:
include/linux/mm.h:1165:12: note: expected ‘struct vm_area_struct *’ but argument is of type ‘long unsigned int’
extern int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
^
arch/arm/xenomai/machine.c:38:4: error: too few arguments to function ‘handle_mm_fault’
handle_mm_fault(vma, addr, flags);
^
In file included from arch/arm/xenomai/machine.c:21:0:
include/linux/mm.h:1165:12: note: declared here
extern int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
scripts/Makefile.build:258: recipe for target 'arch/arm/xenomai/machine.o' failed
next reply other threads:[~2017-05-15 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 14:43 Giulio Moro [this message]
2017-05-15 14:56 ` [Xenomai] too few arguments to function ‘handle_mm_fault` Philippe Gerum
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=DB6PR0701MB24563716802B31DB4E93C0F0B5E10@DB6PR0701MB2456.eurprd07.prod.outlook.com \
--to=g.moro@qmul.ac.uk \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.