public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [arm-integrator:b4/aarch64-clear-pages 2/2] make[7]: *** No rule to make target 'arch/arm64/kvm/hyp/nvhe/../../../lib/clear_page.nvhe.o', needed by 'arch/arm64/kvm/hyp/nvhe/kvm_nvhe.tmp.o'.
Date: Sat, 14 Feb 2026 14:25:43 -0500	[thread overview]
Message-ID: <20260214192543.GA2633863@ax162> (raw)
In-Reply-To: <CAD++jLmmnNP-x80wT5HGTar0VghXZxsU_kYdcsvZH2nkbtp2sA@mail.gmail.com>

On Sat, Feb 14, 2026 at 06:10:19PM +0100, Linus Walleij wrote:
> On Sat, Feb 14, 2026 at 1:54 PM kernel test robot <lkp@intel.com> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-integrator.git b4/aarch64-clear-pages
> > head:   a925ec351435c4da7f3ca8877af9e0aee81bcca5
> > commit: a925ec351435c4da7f3ca8877af9e0aee81bcca5 [2/2] arm64: Implement clear_pages()
> > config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260214/202602142051.bzpo4KnU-lkp@intel.com/config)
> > compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260214/202602142051.bzpo4KnU-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/202602142051.bzpo4KnU-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > >> make[7]: *** No rule to make target 'arch/arm64/kvm/hyp/nvhe/../../../lib/clear_page.nvhe.o', needed by 'arch/arm64/kvm/hyp/nvhe/kvm_nvhe.tmp.o'.
> >    make[7]: Target 'arch/arm64/kvm/hyp/nvhe/' not remade because of errors.
> 
> What is this?

This is reproducible with a clean out folder. Your patch renamed
clear_page.S to clear_pages.S and you handled that properly in
arch/arm64/lib/Makefile but arch/arm64/kvm/hyp/nvhe also uses this
file, so the rename needs to be handled there as well.

diff --git a/arch/arm64/kvm/hyp/nvhe/Makefile b/arch/arm64/kvm/hyp/nvhe/Makefile
index a244ec25f8c5..f857dac82a88 100644
--- a/arch/arm64/kvm/hyp/nvhe/Makefile
+++ b/arch/arm64/kvm/hyp/nvhe/Makefile
@@ -17,7 +17,7 @@ ccflags-y += -fno-stack-protector	\
 hostprogs := gen-hyprel
 HOST_EXTRACFLAGS += -I$(objtree)/include
 
-lib-objs := clear_page.o copy_page.o memcpy.o memset.o
+lib-objs := clear_pages.o copy_page.o memcpy.o memset.o
 lib-objs := $(addprefix ../../../lib/, $(lib-objs))
 
 CFLAGS_switch.nvhe.o += -Wno-override-init

  reply	other threads:[~2026-02-14 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14 12:53 [arm-integrator:b4/aarch64-clear-pages 2/2] make[7]: *** No rule to make target 'arch/arm64/kvm/hyp/nvhe/../../../lib/clear_page.nvhe.o', needed by 'arch/arm64/kvm/hyp/nvhe/kvm_nvhe.tmp.o' kernel test robot
2026-02-14 17:10 ` Linus Walleij
2026-02-14 19:25   ` Nathan Chancellor [this message]
2026-02-16  0:21     ` Linus Walleij

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=20260214192543.GA2633863@ax162 \
    --to=nathan@kernel.org \
    --cc=linusw@kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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