From: hejianet@gmail.com (Jia He)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/5] mm: page_alloc: remain memblock_next_valid_pfn() on arm and arm64
Date: Wed, 4 Apr 2018 22:34:41 +0800 [thread overview]
Message-ID: <dbc4a381-c952-6806-ed0d-b2a33748e7ac@gmail.com> (raw)
In-Reply-To: <201804042156.YTVq2WAJ%fengguang.wu@intel.com>
sorry, will fix it right now
Cheer,
Jia
On 4/4/2018 10:19 PM, kbuild test robot Wrote:
> Hi Jia,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on v4.16 next-20180403]
> [cannot apply to linus/master mmotm/master]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Jia-He/mm-page_alloc-remain-memblock_next_valid_pfn-on-arm-and-arm64/20180404-200732
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> config: i386-randconfig-x013-201813 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from include/linux/gfp.h:6:0,
> from include/linux/mm.h:10,
> from mm/page_alloc.c:18:
> mm/page_alloc.c: In function 'memmap_init_zone':
>>> include/linux/mmzone.h:1299:28: error: called object is not a function or function pointer
> #define next_valid_pfn (pfn++)
> ~~~~^~~
>>> mm/page_alloc.c:5349:39: note: in expansion of macro 'next_valid_pfn'
> for (pfn = start_pfn; pfn < end_pfn; next_valid_pfn(pfn)) {
> ^~~~~~~~~~~~~~
>
> vim +1299 include/linux/mmzone.h
>
> 1296
> 1297 /* fallback to default defitions*/
> 1298 #ifndef next_valid_pfn
>> 1299 #define next_valid_pfn (pfn++)
> 1300 #endif
> 1301
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Cheers,
Jia
next prev parent reply other threads:[~2018-04-04 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 2:56 [PATCH v6 0/5] optimize memblock_next_valid_pfn and early_pfn_valid on arm and arm64 Jia He
2018-04-04 2:56 ` [PATCH v6 1/5] mm: page_alloc: remain memblock_next_valid_pfn() " Jia He
2018-04-04 14:19 ` kbuild test robot
2018-04-04 14:34 ` Jia He [this message]
2018-04-04 2:56 ` [PATCH v6 2/5] arm: arm64: page_alloc: reduce unnecessary binary search in memblock_next_valid_pfn() Jia He
2018-04-04 2:56 ` [PATCH v6 3/5] mm/memblock: introduce memblock_search_pfn_regions() Jia He
2018-04-04 2:56 ` [PATCH v6 4/5] arm: arm64: introduce pfn_valid_region() Jia He
2018-04-04 2:56 ` [PATCH v6 5/5] mm: page_alloc: reduce unnecessary binary search in early_pfn_valid() Jia He
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=dbc4a381-c952-6806-ed0d-b2a33748e7ac@gmail.com \
--to=hejianet@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).