From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Nhat Pham <nphamcs@gmail.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 153/301] mm/list_lru.c:110:1: error: unused function 'list_lru_from_kmem'
Date: Thu, 14 Dec 2023 07:35:53 -0800 [thread overview]
Message-ID: <20231214073553.0c2ce9ad2ed0a56d66021c7b@linux-foundation.org> (raw)
In-Reply-To: <202312141318.q8b5yrAq-lkp@intel.com>
On Thu, 14 Dec 2023 13:09:31 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: 3ecae30dda241440417499d69ae90dfad517a932
> commit: 0a97c01cd20bb96359d8c9dedad92a061ed34e0b [153/301] list_lru: allow explicit memcg and NUMA node selection
> config: x86_64-sof-customedconfig-compile-test-defconfig (https://download.01.org/0day-ci/archive/20231214/202312141318.q8b5yrAq-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231214/202312141318.q8b5yrAq-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/202312141318.q8b5yrAq-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> mm/list_lru.c:110:1: error: unused function 'list_lru_from_kmem' [-Werror,-Wunused-function]
> list_lru_from_kmem(struct list_lru *lru, int nid, void *ptr,
> ^
> 1 error generated.
Thanks, I queued a fix to remove that function.
prev parent reply other threads:[~2023-12-14 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 5:09 kernel test robot
2023-12-14 15:35 ` Andrew Morton [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=20231214073553.0c2ce9ad2ed0a56d66021c7b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nphamcs@gmail.com \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox