From: Alexandre Ghiti <alex@ghiti.fr>
To: John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Anders Roxell <anders.roxell@linaro.org>,
Andrew Jones <ajones@ventanamicro.com>,
Andy Chiu <andy.chiu@sifive.com>, Evan Green <evan@rivosinc.com>,
Hugh Dickins <hughd@google.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Qinglin Pan <panqinglin2020@iscas.ac.cn>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/riscv: fix potential build failure during the "emit_tests" step
Date: Thu, 13 Jul 2023 13:51:01 +0200 [thread overview]
Message-ID: <f903634d-851f-af64-8d9a-6b13d813587c@ghiti.fr> (raw)
In-Reply-To: <20230712193514.740033-1-jhubbard@nvidia.com>
Hi John,
On 12/07/2023 21:35, John Hubbard wrote:
> The riscv selftests (which were modeled after the arm64 selftests) are
> improperly declaring the "emit_tests" target to depend upon the "all"
> target. This approach, when combined with commit 9fc96c7c19df
> ("selftests: error out if kernel header files are not yet built"), has
> caused build failures [1] on arm64, and is likely to cause similar
> failures for riscv.
>
> To fix this, simply remove the unnecessary "all" dependency from the
> emit_tests target. The dependency is still effectively honored, because
> again, invocation is via "install", which also depends upon "all".
>
> An alternative approach would be to harden the emit_tests target so that
> it can depend upon "all", but that's a lot more complicated and hard to
> get right, and doesn't seem worth it, especially given that emit_tests
> should probably not be overridden at all.
>
> [1] https://lore.kernel.org/20230710-kselftest-fix-arm64-v1-1-48e872844f25@kernel.org
>
> Fixes: 9fc96c7c19df ("selftests: error out if kernel header files are not yet built")
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
>
> Andrew,
>
> With this, and with my arm64 fix [2] that you've already put into
> mm-unstable, you should be able to safely drop commit 819187ab8741
> ("selftests: fix arm64 test installation").
>
> [2] https://lore.kernel.org/20230711005629.2547838-1-jhubbard@nvidia.com
>
> thanks,
> John Hubbard
>
>
> tools/testing/selftests/riscv/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/riscv/Makefile b/tools/testing/selftests/riscv/Makefile
> index 9dd629cc86aa..f4b3d5c9af5b 100644
> --- a/tools/testing/selftests/riscv/Makefile
> +++ b/tools/testing/selftests/riscv/Makefile
> @@ -43,7 +43,7 @@ run_tests: all
> done
>
> # Avoid any output on non riscv on emit_tests
> -emit_tests: all
> +emit_tests:
> @for DIR in $(RISCV_SUBTARGETS); do \
> BUILD_TARGET=$(OUTPUT)/$$DIR; \
> $(MAKE) OUTPUT=$$BUILD_TARGET -C $$DIR $@; \
>
> base-commit: 3f01e9fed8454dcd89727016c3e5b2fbb8f8e50c
> prerequisite-patch-id: 37c92f7425689ff069fb83996a25cd98e78d7242
Perfect timing, I have just encountered this failure this morning:
make[5]: *** [../../lib.mk:81: kernel_header_files] Error 1
that your patch fixed :) So you can add:
Tested-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Thank you!
Alex
next prev parent reply other threads:[~2023-07-13 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 19:35 John Hubbard
2023-07-13 11:51 ` Alexandre Ghiti [this message]
2023-08-03 14:45 ` Palmer Dabbelt
2023-08-03 16:48 ` Shuah Khan
2023-08-03 15:10 ` patchwork-bot+linux-riscv
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=f903634d-851f-af64-8d9a-6b13d813587c@ghiti.fr \
--to=alex@ghiti.fr \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=anders.roxell@linaro.org \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=evan@rivosinc.com \
--cc=hughd@google.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=panqinglin2020@iscas.ac.cn \
--cc=paul.walmsley@sifive.com \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.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