From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: vDSO: don't include generated headers for chacha test
Date: Wed, 4 Sep 2024 13:19:29 -0300 [thread overview]
Message-ID: <9f12f377-0fd7-4178-b940-7917094ff2cb@linaro.org> (raw)
In-Reply-To: <20240904155817.1153783-1-Jason@zx2c4.com>
On 04/09/24 12:58, Jason A. Donenfeld wrote:
> It's not correct to use $(top_srcdir) for generated header files, for
> builds that are done out of tree via O=, and $(objtree) isn't valid in
> the selftests context. Instead, just obviate the need for these
> generated header files by defining empty stubs in tools/include/asm,
> which is the same thing that's done for rwlock.h.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Works for me, thanks.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> ---
> tools/include/asm/asm-offsets.h | 0
> tools/include/asm/cpucap-defs.h | 0
> tools/include/asm/sysreg-defs.h | 0
> tools/testing/selftests/vDSO/Makefile | 1 -
> 4 files changed, 1 deletion(-)
> create mode 100644 tools/include/asm/asm-offsets.h
> create mode 100644 tools/include/asm/cpucap-defs.h
> create mode 100644 tools/include/asm/sysreg-defs.h
>
> diff --git a/tools/include/asm/asm-offsets.h b/tools/include/asm/asm-offsets.h
> new file mode 100644
> index 000000000000..e69de29bb2d1
> diff --git a/tools/include/asm/cpucap-defs.h b/tools/include/asm/cpucap-defs.h
> new file mode 100644
> index 000000000000..e69de29bb2d1
> diff --git a/tools/include/asm/sysreg-defs.h b/tools/include/asm/sysreg-defs.h
> new file mode 100644
> index 000000000000..e69de29bb2d1
> diff --git a/tools/testing/selftests/vDSO/Makefile b/tools/testing/selftests/vDSO/Makefile
> index 3c6fafbd83a6..55038a65fa61 100644
> --- a/tools/testing/selftests/vDSO/Makefile
> +++ b/tools/testing/selftests/vDSO/Makefile
> @@ -40,6 +40,5 @@ $(OUTPUT)/vdso_test_getrandom: CFLAGS += -isystem $(top_srcdir)/tools/include \
> $(OUTPUT)/vdso_test_chacha: $(top_srcdir)/tools/arch/$(SRCARCH)/vdso/vgetrandom-chacha.S
> $(OUTPUT)/vdso_test_chacha: CFLAGS += -idirafter $(top_srcdir)/tools/include \
> -idirafter $(top_srcdir)/arch/$(SRCARCH)/include \
> - -idirafter $(top_srcdir)/arch/$(SRCARCH)/include/generated \
> -idirafter $(top_srcdir)/include \
> -D__ASSEMBLY__ -Wa,--noexecstack
next prev parent reply other threads:[~2024-09-04 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 15:58 Jason A. Donenfeld
2024-09-04 16:19 ` Adhemerval Zanella Netto [this message]
2024-09-10 22:52 ` Aishwarya TCV
2024-09-11 2:44 ` Jason A. Donenfeld
2024-09-11 10:14 ` Mark Brown
2024-09-11 12:47 ` Jason A. Donenfeld
2024-09-11 13:01 ` Jason A. Donenfeld
2024-09-11 13:33 ` Jason A. Donenfeld
2024-09-11 13:36 ` [PATCH v2] " Jason A. Donenfeld
2024-09-11 14:12 ` Mark Brown
2024-09-11 14:40 ` Jason A. Donenfeld
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=9f12f377-0fd7-4178-b940-7917094ff2cb@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®