From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: "Ho-Ren (Jack) Chuang" <horenchuang@bytedance.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [akpm-mm:mm-unstable 262/270] vmscan.c:(.text+0x2c90): multiple definition of `mt_find_alloc_memory_type'; kernel/sched/fair.o:fair.c:(.text+0x1db4): first defined here
Date: Mon, 1 Apr 2024 11:20:12 -0700 [thread overview]
Message-ID: <20240401112012.58634114b0e76e062fad7bc0@linux-foundation.org> (raw)
In-Reply-To: <202403311952.oxw8fSed-lkp@intel.com>
OK, thanks. I'll drop
Patch series "Improved Memory Tier Creation for CPUless NUMA Nodes", v9.
and shall await a v10.
next prev parent reply other threads:[~2024-04-01 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 12:05 kernel test robot
2024-04-01 18:20 ` Andrew Morton [this message]
2024-04-01 18:23 ` [External] " Ho-Ren (Jack) Chuang
2024-04-01 23:03 ` Ho-Ren (Jack) Chuang
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=20240401112012.58634114b0e76e062fad7bc0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=horenchuang@bytedance.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ying.huang@intel.com \
/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