From: Stafford Horne <shorne@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
linux-openrisc@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] usr/include: openrisc: don't HDRTEST bpf_perf_event.h
Date: Sat, 26 Apr 2025 07:00:24 +0100 [thread overview]
Message-ID: <aAx2eAa2yyjabL2L@antec> (raw)
In-Reply-To: <20250426030815.1310875-1-rdunlap@infradead.org>
Hi Randy,
On Fri, Apr 25, 2025 at 08:08:15PM -0700, Randy Dunlap wrote:
> Since openrisc does not support PERF_EVENTS, omit the HDRTEST of
> bpf_perf_event.h for arch/openrisc/.
>
> Fixes a build error:
> usr/include/linux/bpf_perf_event.h:14:28: error: field 'regs' has incomplete type
This looks ok to me, but do you have any pointer of how to reproduce this?
-Stafford
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Masahiro Yamada <masahiroy@kernel.org>
> Cc: Jonas Bonn <jonas@southpole.se>
> Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> Cc: Stafford Horne <shorne@gmail.com>
> Cc: linux-openrisc@vger.kernel.org
> Cc: linux-kbuild@vger.kernel.org
> ---
> usr/include/Makefile | 4 ++++
> 1 file changed, 4 insertions(+)
>
> --- linux-next-20250424.orig/usr/include/Makefile
> +++ linux-next-20250424/usr/include/Makefile
> @@ -59,6 +59,10 @@ ifeq ($(SRCARCH),arc)
> no-header-test += linux/bpf_perf_event.h
> endif
>
> +ifeq ($(SRCARCH),openrisc)
> +no-header-test += linux/bpf_perf_event.h
> +endif
> +
> ifeq ($(SRCARCH),powerpc)
> no-header-test += linux/bpf_perf_event.h
> endif
next prev parent reply other threads:[~2025-04-26 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 3:08 [PATCH] usr/include: openrisc: don't HDRTEST bpf_perf_event.h Randy Dunlap
2025-04-26 6:00 ` Stafford Horne [this message]
2025-04-26 15:45 ` Randy Dunlap
2025-04-26 16:14 ` Stafford Horne
2025-05-03 16:01 ` Masahiro Yamada
2025-05-03 16:13 ` Masahiro Yamada
2025-05-03 23:23 ` Randy Dunlap
2025-05-03 23:31 ` Masahiro Yamada
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=aAx2eAa2yyjabL2L@antec \
--to=shorne@gmail.com \
--cc=jonas@southpole.se \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.org \
--cc=stefan.kristiansson@saunalahti.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.