From: kbuild test robot <lkp@intel.com>
To: Arun KS <arunks@codeaurora.org>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Oscar Salvador <osalvador@suse.de>
Subject: [mmotm:master 204/302] mm/memory_hotplug.c:637:17: error: lvalue required as left operand of assignment
Date: Sat, 15 Dec 2018 14:02:40 +0800 [thread overview]
Message-ID: <201812151435.uS2wvUla%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 6d5b029d523e959579667282e713106a29c193d2
commit: cfe730f86623d820289f9adb76fd5084d7767431 [204/302] mm/page_alloc.c: memory hotplug: free pages as higher order
config: x86_64-rhel-7.2-clear (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout cfe730f86623d820289f9adb76fd5084d7767431
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the mmotm/master HEAD 6d5b029d523e959579667282e713106a29c193d2 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
mm/memory_hotplug.c: In function 'generic_online_page':
>> mm/memory_hotplug.c:637:17: error: lvalue required as left operand of assignment
totalram_pages += (1UL << order);
^~
vim +637 mm/memory_hotplug.c
633
634 static int generic_online_page(struct page *page, unsigned int order)
635 {
636 __free_pages_core(page, order);
> 637 totalram_pages += (1UL << order);
638 #ifdef CONFIG_HIGHMEM
639 if (PageHighMem(page))
640 totalhigh_pages += (1UL << order);
641 #endif
642 return 0;
643 }
644
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41457 bytes --]
reply other threads:[~2018-12-15 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201812151435.uS2wvUla%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/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