From: kbuild test robot <fengguang.wu@intel.com>
To: "Jérôme Glisse" <jglisse@redhat.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Evgeny Baskakov <ebaskakov@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Mark Hairgrove <mhairgrove@nvidia.com>,
Sherry Cheung <SCheung@nvidia.com>,
Subhash Gutti <sgutti@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 265/276] mm/hmm.c:33:0: warning: "SECTION_SIZE" redefined
Date: Sun, 9 Apr 2017 11:21:37 +0800 [thread overview]
Message-ID: <201704091134.IiV9xYC5%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 5b220005fda0593464fc4549eea586e597bf783c
commit: 89cc4c46458ccdfab15b2fe94a5645766d5091aa [265/276] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 89cc4c46458ccdfab15b2fe94a5645766d5091aa
# save the attached .config to linux build tree
make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
>> mm/hmm.c:33:0: warning: "SECTION_SIZE" redefined
#define SECTION_SIZE (1UL << PA_SECTION_SHIFT)
In file included from arch/arm64/include/asm/processor.h:36:0,
from arch/arm64/include/asm/spinlock.h:21,
from include/linux/spinlock.h:87,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:5,
from include/linux/mm.h:9,
from mm/hmm.c:20:
arch/arm64/include/asm/pgtable-hwdef.h:87:0: note: this is the location of the previous definition
#define SECTION_SIZE (_AC(1, UL) << SECTION_SHIFT)
mm/hmm.c: In function 'hmm_devmem_release':
mm/hmm.c:815:2: error: implicit declaration of function 'arch_remove_memory' [-Werror=implicit-function-declaration]
arch_remove_memory(align_start, align_size, devmem->pagemap.type);
^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/SECTION_SIZE +33 mm/hmm.c
17 * Refer to include/linux/hmm.h for information about heterogeneous memory
18 * management or HMM for short.
19 */
20 #include <linux/mm.h>
21 #include <linux/hmm.h>
22 #include <linux/rmap.h>
23 #include <linux/swap.h>
24 #include <linux/slab.h>
25 #include <linux/sched.h>
26 #include <linux/mmzone.h>
27 #include <linux/pagemap.h>
28 #include <linux/swapops.h>
29 #include <linux/hugetlb.h>
30 #include <linux/memremap.h>
31 #include <linux/mmu_notifier.h>
32
> 33 #define SECTION_SIZE (1UL << PA_SECTION_SHIFT)
34
35 static const struct mmu_notifier_ops hmm_mmu_notifier_ops;
36
37
38 /*
39 * struct hmm - HMM per mm struct
40 *
41 * @mm: mm struct this HMM struct is bound to
---
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: 55227 bytes --]
reply other threads:[~2017-04-09 3:22 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=201704091134.IiV9xYC5%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=SCheung@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ebaskakov@nvidia.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhairgrove@nvidia.com \
--cc=sgutti@nvidia.com \
/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