From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Stefan Roesch <shr@devkernel.io>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7414/8213] mm/ksm.c:344:13: warning: 'set_advisor_defaults' defined but not used
Date: Fri, 15 Dec 2023 11:10:10 -0800 [thread overview]
Message-ID: <20231215111010.bbab9d6e80f43302d60c7e42@linux-foundation.org> (raw)
In-Reply-To: <202312151854.4k8dhWf6-lkp@intel.com>
On Fri, 15 Dec 2023 18:36:51 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 17cb8a20bde66a520a2ca7aad1063e1ce7382240
> commit: 5898c0939406116f8ab33dc5a50d36f3b5d44863 [7414/8213] mm/ksm: add sysfs knobs for advisor
> config: openrisc-randconfig-r016-20230621 (https://download.01.org/0day-ci/archive/20231215/202312151854.4k8dhWf6-lkp@intel.com/config)
> compiler: or1k-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312151854.4k8dhWf6-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202312151854.4k8dhWf6-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> mm/ksm.c:344:13: warning: 'set_advisor_defaults' defined but not used [-Wunused-function]
> 344 | static void set_advisor_defaults(void)
Thanks. It looks like there's a bunch of advisor code and storage
which can go away if CONFIG_SYSFS=n?
next prev parent reply other threads:[~2023-12-15 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 10:36 kernel test robot
2023-12-15 19:10 ` Andrew Morton [this message]
2023-12-15 19:13 ` Stefan Roesch
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=20231215111010.bbab9d6e80f43302d60c7e42@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shr@devkernel.io \
/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