From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: bpf@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH powerpc v2] powerpc/bpf: Fix use of user_pt_regs in uapi
Date: Wed, 29 Jun 2022 22:14:09 +1000 [thread overview]
Message-ID: <165650484996.3003821.13352352877965822708.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220627191119.142867-1-naveen.n.rao@linux.vnet.ibm.com>
On Tue, 28 Jun 2022 00:41:19 +0530, Naveen N. Rao wrote:
> Trying to build a .c file that includes <linux/bpf_perf_event.h>:
> $ cat test_bpf_headers.c
> #include <linux/bpf_perf_event.h>
>
> throws the below error:
> /usr/include/linux/bpf_perf_event.h:14:28: error: field ‘regs’ has incomplete type
> 14 | bpf_user_pt_regs_t regs;
> | ^~~~
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc/bpf: Fix use of user_pt_regs in uapi
https://git.kernel.org/powerpc/c/b21bd5a4b130f8370861478d2880985daace5913
cheers
prev parent reply other threads:[~2022-06-29 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 19:11 [PATCH powerpc v2] powerpc/bpf: Fix use of user_pt_regs in uapi Naveen N. Rao
2022-06-29 12:14 ` Michael Ellerman [this message]
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=165650484996.3003821.13352352877965822708.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=bpf@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).