From: Mark Brown <broonie@kernel.org>
To: Peter Xu <peterx@redhat.com>, John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-next@vger.kernel.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Steven Price <steven.price@arm.com>
Subject: Build failure in -next with get_user_pages_remote() API change
Date: Fri, 10 Jul 2020 12:32:01 +0100 [thread overview]
Message-ID: <20200710113201.GC5653@sirena.org.uk> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 720 bytes --]
Today's -next fails to build in various arm64 configs with:
arch/arm64/kernel/mte.c:225:23: error: too many arguments to function call, expected 7, have 8
&page, &vma, NULL);
^~~~
./include/linux/stddef.h:8:14: note: expanded from macro 'NULL'
#define NULL ((void *)0)
^~~~~~~~~~~
./include/linux/mm.h:1705:6: note: 'get_user_pages_remote' declared here
long get_user_pages_remote(struct mm_struct *mm,
^
1 error generated.
caused by b7363b0ab88d66d3c (mm/gup: remove task_struct pointer for all
gup code) which updated the signature of get_user_pages_remote() without
updating the caller in mte.c.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-07-10 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 11:32 Mark Brown [this message]
2020-07-10 12:24 ` Build failure in -next with get_user_pages_remote() API change Peter Xu
2020-07-10 13:38 ` Peter Xu
2020-07-10 15:23 ` Catalin Marinas
2020-07-10 22:28 ` Andrew Morton
2020-07-23 18:10 ` Catalin Marinas
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=20200710113201.GC5653@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=jhubbard@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=steven.price@arm.com \
--cc=will@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).