From: Nathan Chancellor <nathan@kernel.org>
To: David Hildenbrand <david@redhat.com>, kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 10023/11721] include/linux/memory_hotplug.h:312:26: warning: unused parameter 'group'
Date: Mon, 6 Sep 2021 11:46:56 -0700 [thread overview]
Message-ID: <ece61908-f8eb-4c45-5d5f-bfc52f3b8f45@kernel.org> (raw)
In-Reply-To: <8e405e43-c5f0-d58b-e38a-fe19f97c3333@redhat.com>
On 9/6/2021 3:35 AM, David Hildenbrand wrote:
>> include/linux/memory_hotplug.h:311:47: warning: unused parameter
>> 'start_pfn' [-Wunused-parameter]
>> static inline int offline_pages(unsigned long start_pfn, unsigned
>> long nr_pages,
>> ^
>> include/linux/memory_hotplug.h:311:72: warning: unused parameter
>> 'nr_pages' [-Wunused-parameter]
>> static inline int offline_pages(unsigned long start_pfn, unsigned
>> long nr_pages,
>>
>> ^
>>>> include/linux/memory_hotplug.h:312:26: warning: unused parameter
>>>> 'group' [-Wunused-parameter]
>> struct memory_group *group)
>
> What a bunch of useless warnings ...
>
> Nothing to fix here.
Sorry for the noise, it is a known issue with this randconfig :/
https://lore.kernel.org/r/YSQE2f5teuvKLkON@Ryzen-9-3900X.localdomain/
https://lore.kernel.org/r/20210824022640.2170859-1-nathan@kernel.org/
Cheers,
Nathan
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <nathan@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 10023/11721] include/linux/memory_hotplug.h:312:26: warning: unused parameter 'group'
Date: Mon, 06 Sep 2021 11:46:56 -0700 [thread overview]
Message-ID: <ece61908-f8eb-4c45-5d5f-bfc52f3b8f45@kernel.org> (raw)
In-Reply-To: <8e405e43-c5f0-d58b-e38a-fe19f97c3333@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On 9/6/2021 3:35 AM, David Hildenbrand wrote:
>> include/linux/memory_hotplug.h:311:47: warning: unused parameter
>> 'start_pfn' [-Wunused-parameter]
>> static inline int offline_pages(unsigned long start_pfn, unsigned
>> long nr_pages,
>> ^
>> include/linux/memory_hotplug.h:311:72: warning: unused parameter
>> 'nr_pages' [-Wunused-parameter]
>> static inline int offline_pages(unsigned long start_pfn, unsigned
>> long nr_pages,
>>
>> ^
>>>> include/linux/memory_hotplug.h:312:26: warning: unused parameter
>>>> 'group' [-Wunused-parameter]
>> struct memory_group *group)
>
> What a bunch of useless warnings ...
>
> Nothing to fix here.
Sorry for the noise, it is a known issue with this randconfig :/
https://lore.kernel.org/r/YSQE2f5teuvKLkON(a)Ryzen-9-3900X.localdomain/
https://lore.kernel.org/r/20210824022640.2170859-1-nathan(a)kernel.org/
Cheers,
Nathan
next prev parent reply other threads:[~2021-09-06 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 3:47 [linux-next:master 10023/11721] include/linux/memory_hotplug.h:312:26: warning: unused parameter 'group' kernel test robot
2021-09-06 3:47 ` kernel test robot
2021-09-06 10:35 ` David Hildenbrand
2021-09-06 10:35 ` David Hildenbrand
2021-09-06 18:46 ` Nathan Chancellor [this message]
2021-09-06 18:46 ` Nathan Chancellor
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=ece61908-f8eb-4c45-5d5f-bfc52f3b8f45@kernel.org \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.