From: kbuild test robot <lkp@intel.com>
To: Dennis Chen <dennis.chen@arm.com>
Cc: kbuild-all@01.org, linux-arm-kernel@lists.infradead.org,
nd@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
Steve Capper <steve.capper@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
linux-mm@kvack.org, linux-acpi@vger.kernel.org,
linux-efi@vger.kernel.org
Subject: Re: [PATCH v4 2/3] mm: memblock Add some new functions to address the mem limit issue
Date: Tue, 28 Jun 2016 18:14:31 +0800 [thread overview]
Message-ID: <201606281837.baLUZlDs%fengguang.wu@intel.com> (raw)
In-Reply-To: <1467107137-29631-2-git-send-email-dennis.chen@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
Hi,
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on v4.7-rc5 next-20160627]
[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/Dennis-Chen/mm-memblock-enhence-the-memblock-debugfs-output/20160628-174951
base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: i386-randconfig-i0-201626 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
mm/memblock.c: In function 'memblock_enforce_memory_limit':
>> mm/memblock.c:1489:26: warning: unused variable 'r' [-Wunused-variable]
struct memblock_region *r;
^
vim +/r +1489 mm/memblock.c
1473 * of those regions, max_addr will keep original value ULLONG_MAX
1474 */
1475 for_each_memblock(memory, r) {
1476 if (limit <= r->size) {
1477 max_addr = r->base + limit;
1478 break;
1479 }
1480 limit -= r->size;
1481 }
1482
1483 return max_addr;
1484 }
1485
1486 void __init memblock_enforce_memory_limit(phys_addr_t limit)
1487 {
1488 phys_addr_t max_addr = (phys_addr_t)ULLONG_MAX;
> 1489 struct memblock_region *r;
1490
1491 if (!limit)
1492 return;
1493
1494 max_addr = __find_max_addr(limit);
1495
1496 /* @limit exceeds the total size of the memory, do nothing */
1497 if (max_addr == (phys_addr_t)ULLONG_MAX)
---
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: 24789 bytes --]
prev parent reply other threads:[~2016-06-28 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 9:45 [PATCH v4 1/3] mm: memblock enhence the memblock debugfs output Dennis Chen
2016-06-28 9:45 ` [PATCH v4 2/3] mm: memblock Add some new functions to address the mem limit issue Dennis Chen
2016-06-28 10:14 ` kbuild test robot [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=201606281837.baLUZlDs%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dennis.chen@arm.com \
--cc=kbuild-all@01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=nd@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.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