From: kbuild test robot <lkp@intel.com>
To: Waiman Long <longman@redhat.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Oscar Salvador <osalvador@suse.de>,
Tejun Heo <tj@kernel.org>, Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v3] include/linux/nodemask.h: Use nr_node_ids (not MAX_NUMNODES) in __nodemask_pr_numnodes()
Date: Fri, 21 Dec 2018 08:39:57 +0800 [thread overview]
Message-ID: <201812210836.SVZGQPJS%fengguang.wu@intel.com> (raw)
In-Reply-To: <1545253492-32070-1-git-send-email-longman@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]
Hi Waiman,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.20-rc7 next-20181220]
[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/Waiman-Long/include-linux-nodemask-h-Use-nr_node_ids-not-MAX_NUMNODES-in-__nodemask_pr_numnodes/20181221-082352
config: riscv-tinyconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=riscv
All warnings (new ones prefixed by >>):
In file included from include/linux/sched.h:22,
from arch/riscv/kernel/asm-offsets.c:18:
>> include/linux/nodemask.h:492: warning: "nr_node_ids" redefined
#define nr_node_ids 1
include/linux/nodemask.h:105: note: this is the location of the previous definition
#define nr_node_ids MAX_NUMNODES
vim +/nr_node_ids +492 include/linux/nodemask.h
13808910 Christoph Lameter 2007-10-16 485
13808910 Christoph Lameter 2007-10-16 486 #define for_each_node_state(node, __state) \
13808910 Christoph Lameter 2007-10-16 487 for ( (node) = 0; (node) == 0; (node) = 1)
13808910 Christoph Lameter 2007-10-16 488
8357f869 KAMEZAWA Hiroyuki 2006-03-27 489 #define first_online_node 0
8d060bf4 David Rientjes 2014-08-06 490 #define first_memory_node 0
8357f869 KAMEZAWA Hiroyuki 2006-03-27 491 #define next_online_node(nid) (MAX_NUMNODES)
74c7aa8b Christoph Lameter 2007-02-20 @492 #define nr_node_ids 1
62bc62a8 Christoph Lameter 2009-06-16 493 #define nr_online_nodes 1
13808910 Christoph Lameter 2007-10-16 494
:::::: The code at line 492 was first introduced by commit
:::::: 74c7aa8b8581e0ba8d6d17c623b9279aaabbb0cf [PATCH] Replace highest_possible_node_id() with nr_node_ids
:::::: TO: Christoph Lameter <clameter@sgi.com>
:::::: CC: Linus Torvalds <torvalds@woody.linux-foundation.org>
---
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: 4416 bytes --]
prev parent reply other threads:[~2018-12-21 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 21:04 Waiman Long
2018-12-21 0:39 ` 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=201812210836.SVZGQPJS%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=osalvador@suse.de \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®