linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Joao Martins <joao.m.martins@oracle.com>,
	Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: [linux-next:master 3093/3958] drivers/acpi/numa/hmat.c:658: undefined reference to `hmem_register_device'
Date: Mon, 31 Aug 2020 12:38:02 -0700	[thread overview]
Message-ID: <20200831123802.e23a24b03ef54bfd5091ecff@linux-foundation.org> (raw)
In-Reply-To: <202008311538.99SbVGFx%lkp@intel.com>


(cc Vishal & Joao)

On Mon, 31 Aug 2020 15:11:42 +0800 kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   b36c969764ab12faebb74711c942fa3e6eaf1e96
> commit: f7782cc946fea99b8a4a0a83b6c3775a6beff8ce [3093/3958] ACPI: HMAT: refactor hmat_register_target_device to hmem_register_device
> config: arm64-randconfig-r016-20200831 (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 9.3.0
> 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
>         git checkout f7782cc946fea99b8a4a0a83b6c3775a6beff8ce
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    aarch64-linux-ld: drivers/acpi/numa/hmat.o: in function `hmat_register_target_devices':
> >> drivers/acpi/numa/hmat.c:658: undefined reference to `hmem_register_device'
> 
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f7782cc946fea99b8a4a0a83b6c3775a6beff8ce
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout f7782cc946fea99b8a4a0a83b6c3775a6beff8ce
> vim +658 drivers/acpi/numa/hmat.c
> 
>    643	
>    644	static void hmat_register_target_devices(struct memory_target *target)
>    645	{
>    646		struct resource *res;
>    647	
>    648		/*
>    649		 * Do not bother creating devices if no driver is available to
>    650		 * consume them.
>    651		 */
>    652		if (!IS_ENABLED(CONFIG_DEV_DAX_HMEM))
>    653			return;
>    654	
>    655		for (res = target->memregions.child; res; res = res->sibling) {
>    656			int target_nid = acpi_map_pxm_to_node(target->memory_pxm);
>    657	
>  > 658			hmem_register_device(target_nid, res);
>    659		}
>    660	}
>    661	
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


  reply	other threads:[~2020-08-31 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  7:11 kernel test robot
2020-08-31 19:38 ` Andrew Morton [this message]
2020-09-01 12:57   ` Joao Martins
2020-09-03 12:31     ` Joao Martins

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=20200831123802.e23a24b03ef54bfd5091ecff@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=vishal.l.verma@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