From: kbuild test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, linux-nvdimm@lists.01.org, linux-mm@kvack.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] libnvdimm, pmem: fix 'pfn' support for section-misaligned namespaces
Date: Tue, 1 Mar 2016 11:16:08 +0800 [thread overview]
Message-ID: <201603011110.fmlYKtFn%fengguang.wu@intel.com> (raw)
In-Reply-To: <20160301025626.12812.4840.stgit@dwillia2-desk3.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
Hi Dan,
[auto build test WARNING on v4.5-rc6]
[also build test WARNING on next-20160229]
[cannot apply to linux-nvdimm/libnvdimm-for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Dan-Williams/devm_memremap_pages-vs-section-misaligned-pmem/20160301-105936
config: i386-randconfig-x007-201609 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
drivers/nvdimm/pmem.c: In function 'init_altmap_reserve':
>> drivers/nvdimm/pmem.c:375:16: warning: unused variable 'base_pfn' [-Wunused-variable]
unsigned long base_pfn = __phys_to_pfn(base);
^
vim +/base_pfn +375 drivers/nvdimm/pmem.c
359 /*
360 * We hotplug memory at section granularity, pad the reserved area from
361 * the previous section base to the namespace base address.
362 */
363 static unsigned long init_altmap_base(resource_size_t base)
364 {
365 unsigned long base_pfn = __phys_to_pfn(base);
366
367 #ifdef CONFIG_SPARSEMEM
368 base_pfn = SECTION_ALIGN_DOWN(base_pfn);
369 #endif
370 return base_pfn;
371 }
372
373 static unsigned long init_altmap_reserve(resource_size_t base)
374 {
> 375 unsigned long base_pfn = __phys_to_pfn(base);
376 unsigned long reserve = __phys_to_pfn(SZ_8K);
377
378 #ifdef CONFIG_SPARSEMEM
379 reserve += base_pfn - SECTION_ALIGN_DOWN(base_pfn);
380 #endif
381 return reserve;
382 }
383
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 24045 bytes --]
next prev parent reply other threads:[~2016-03-01 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 2:56 [PATCH 0/2] devm_memremap_pages vs section-misaligned pmem Dan Williams
2016-03-01 2:56 ` [PATCH 1/2] libnvdimm, pmem: fix 'pfn' support for section-misaligned namespaces Dan Williams
2016-03-01 3:16 ` kbuild test robot [this message]
2016-03-01 2:56 ` [PATCH 2/2] mm: fix mixed zone detection in devm_memremap_pages Dan Williams
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=201603011110.fmlYKtFn%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.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