From: kernel test robot <lkp@intel.com>
To: Xin Hao <xhao@linux.alibaba.com>, sj@kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
xhao@linux.alibaba.com
Subject: Re: [PATCH] mm/damon: Remove duplicate get_monitoring_region() definitions
Date: Thu, 8 Sep 2022 06:07:15 +0800 [thread overview]
Message-ID: <202209080600.L5N3msAB-lkp@intel.com> (raw)
In-Reply-To: <20220907112924.65546-1-xhao@linux.alibaba.com>
Hi Xin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.0-rc4 next-20220907]
[cannot apply to akpm-mm/mm-everything]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Xin-Hao/mm-damon-Remove-duplicate-get_monitoring_region-definitions/20220907-193059
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 0066f1b0e27556381402db3ff31f85d2a2265858
config: hexagon-randconfig-r041-20220907 (https://download.01.org/0day-ci/archive/20220908/202209080600.L5N3msAB-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project c55b41d5199d2394dd6cdb8f52180d8b81d809d4)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/28cd0cc7549075eccc95a2c48fbe3bc58f17caee
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Xin-Hao/mm-damon-Remove-duplicate-get_monitoring_region-definitions/20220907-193059
git checkout 28cd0cc7549075eccc95a2c48fbe3bc58f17caee
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash mm/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from mm/damon/reclaim.c:16:
>> mm/damon/ops-common.h:13:23: error: unknown type name 'pmd_t'
void damon_pmdp_mkold(pmd_t *pmd, struct mm_struct *mm, unsigned long addr);
^
1 error generated.
vim +/pmd_t +13 mm/damon/ops-common.h
46c3a0accdc48c mm/damon/prmtv-common.h SeongJae Park 2021-11-05 11
46c3a0accdc48c mm/damon/prmtv-common.h SeongJae Park 2021-11-05 12 void damon_ptep_mkold(pte_t *pte, struct mm_struct *mm, unsigned long addr);
46c3a0accdc48c mm/damon/prmtv-common.h SeongJae Park 2021-11-05 @13 void damon_pmdp_mkold(pmd_t *pmd, struct mm_struct *mm, unsigned long addr);
198f0f4c58b9f4 mm/damon/prmtv-common.h SeongJae Park 2021-11-05 14
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-09-07 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 11:29 Xin Hao
2022-09-07 17:27 ` SeongJae Park
2022-09-07 20:59 ` SeongJae Park
2022-09-08 1:43 ` haoxin
2022-09-08 1:55 ` haoxin
2022-09-07 22:07 ` 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=202209080600.L5N3msAB-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=sj@kernel.org \
--cc=xhao@linux.alibaba.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