From: Michal Hocko <mhocko@suse.com>
To: kbuild test robot <fengguang.wu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Zi Yan <zi.yan@cs.rutgers.edu>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 149/256] mm/migrate.c:1920:46: error: passing argument 2 of 'migrate_pages' from incompatible pointer type
Date: Fri, 5 Jan 2018 10:07:53 +0100 [thread overview]
Message-ID: <20180105090753.GI2801@dhcp22.suse.cz> (raw)
In-Reply-To: <201801051045.4sj2RvmD%fengguang.wu@intel.com>
On Fri 05-01-18 10:56:50, Wu Fengguang wrote:
> tree: git://git.cmpxchg.org/linux-mmotm.git master
> head: 1ceb98996d2504dd4e0bcb5f4cb9009a18cd8aaa
> commit: c714f7da3636f838c8ed46c7c477525c2ea98a0f [149/256] mm, migrate: remove reason argument from new_page_t
> config: x86_64-lkp (attached as .config)
> compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
> reproduce:
> git checkout c714f7da3636f838c8ed46c7c477525c2ea98a0f
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> mm/migrate.c: In function 'migrate_misplaced_page':
> >> mm/migrate.c:1920:46: error: passing argument 2 of 'migrate_pages' from incompatible pointer type [-Werror=incompatible-pointer-types]
> nr_remaining = migrate_pages(&migratepages, alloc_misplaced_dst_page,
> ^~~~~~~~~~~~~~~~~~~~~~~~
> mm/migrate.c:1364:5: note: expected 'struct page * (*)(struct page *, long unsigned int)' but argument is of type 'struct page * (*)(struct page *, long unsigned int, int **)'
> int migrate_pages(struct list_head *from, new_page_t get_new_page,
> ^~~~~~~~~~~~~
> cc1: some warnings being treated as errors
Doh. Yet another follow up fix for mm-migrate-remove-reason-argument-from-new_page_t.patch
---
prev parent reply other threads:[~2018-01-05 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 2:56 kbuild test robot
2018-01-05 9:07 ` Michal Hocko [this message]
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=20180105090753.GI2801@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=zi.yan@cs.rutgers.edu \
/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