From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC arm64] samples/bpf: explicitly exclude sysreg sections with asm macros
Date: Fri, 17 Mar 2017 17:04:36 +0000 [thread overview]
Message-ID: <20170317170436.GL5940@leverpostej> (raw)
In-Reply-To: <383e1626-335b-01fe-5921-5956d7201cf4@arm.com>
On Fri, Mar 17, 2017 at 04:57:20PM +0000, Robin Murphy wrote:
> I'm honestly not sure if I'm serious or not, but:
/me shakes the magic 8 ball...
> diff --git a/samples/bpf/Makefile b/samples/bpf/Makefile
> index 72c58675973e..f52ebad7b096 100644
> --- a/samples/bpf/Makefile
> +++ b/samples/bpf/Makefile
> @@ -154,6 +154,6 @@ $(src)/*.c: verify_target_bpf
> # useless for BPF samples.
> $(obj)/%.o: $(src)/%.c
> $(CLANG) $(NOSTDINC_FLAGS) $(LINUXINCLUDE) $(EXTRA_CFLAGS) \
> - -D__KERNEL__ -D__ASM_SYSREG_H -Wno-unused-value
> -Wno-pointer-sign \
> + -D__KERNEL__ -D'asm(...)' -Wno-unused-value
> -Wno-pointer-sign \
> -Wno-compare-distinct-pointer-types \
> -O2 -emit-llvm -c $< -o -| $(LLC) -march=bpf
> -filetype=obj -o $@
... "Concentrate and ask again".
Thanks,
Mark.
next prev parent reply other threads:[~2017-03-17 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 23:18 [RFC arm64] samples/bpf: explicitly exclude sysreg sections with asm macros Andy Gospodarek
2017-03-10 17:52 ` Will Deacon
2017-03-10 19:26 ` Andy Gospodarek
2017-03-10 20:41 ` Mark Rutland
2017-03-15 18:31 ` Andy Gospodarek
2017-03-15 19:17 ` Mark Rutland
2017-03-15 20:54 ` Andy Gospodarek
2017-03-16 10:42 ` Mark Rutland
2017-03-16 21:04 ` Andy Gospodarek
2017-03-17 11:11 ` Robin Murphy
2017-03-17 13:58 ` Andy Gospodarek
2017-03-17 16:57 ` Robin Murphy
2017-03-17 17:04 ` Mark Rutland [this message]
2017-03-17 17:43 ` Andy Gospodarek
2017-03-17 17:17 ` Mark Rutland
2017-03-10 18:13 ` Mark Rutland
2017-03-10 19:35 ` Andy Gospodarek
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=20170317170436.GL5940@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.