From: kernel test robot <lkp@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH davidhildenbrand] early_node_zone_for_memory_block() can be static
Date: Fri, 28 Jan 2022 06:30:15 +0800 [thread overview]
Message-ID: <20220127223014.GA44143@ca5a2f49b72c> (raw)
In-Reply-To: <202201280621.HyzMsDkU-lkp@intel.com>
drivers/base/memory.c:648:13: warning: symbol 'early_node_zone_for_memory_block' was not declared. Should it be static?
Fixes: 176a3d535903 ("tmp")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/memory.c b/drivers/base/memory.c
index fa20ca42862f4..0b396e4c30667 100644
--- a/drivers/base/memory.c
+++ b/drivers/base/memory.c
@@ -645,7 +645,7 @@ int register_memory(struct memory_block *memory)
return ret;
}
-struct zone *early_node_zone_for_memory_block(int nid, struct memory_block *mem)
+static struct zone *early_node_zone_for_memory_block(int nid, struct memory_block *mem)
{
const unsigned long start_pfn = section_nr_to_pfn(mem->start_section_nr);
const unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block;
prev parent reply other threads:[~2022-01-27 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 22:31 [davidhildenbrand:single_zone 4/4] drivers/base/memory.c:648:13: sparse: sparse: symbol 'early_node_zone_for_memory_block' was not declared. Should it be static? kernel test robot
2022-01-27 22:30 ` kernel 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=20220127223014.GA44143@ca5a2f49b72c \
--to=lkp@intel.com \
--cc=david@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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