From: patchwork-bot+netdevbpf@kernel.org
To: Xu Kuohai <xukuohai@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
catalin.marinas@arm.com, daniel@iogearbox.net, haoluo@google.com,
jakub@cloudflare.com, jean-philippe@linaro.org, jolsa@kernel.org,
john.fastabend@gmail.com, jonathanh@nvidia.com,
kpsingh@kernel.org, martin.lau@linux.dev, song@kernel.org,
sdf@google.com, will@kernel.org, yhs@fb.com, zlim.lnx@gmail.com
Subject: Re: [PATCH bpf-next] bpf, arm64: Fix compile error in dummy_tramp()
Date: Thu, 21 Jul 2022 22:30:14 +0000 [thread overview]
Message-ID: <165844261408.3850.10654235868584356143.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220721121319.2999259-1-xukuohai@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 21 Jul 2022 08:13:19 -0400 you wrote:
> From: Xu Kuohai <xukuohai@huawei.com>
>
> dummy_tramp() uses "lr" to refer to the x30 register, but some assembler
> does not recognize "lr" and reports a build failure:
>
> /tmp/cc52xO0c.s: Assembler messages:
> /tmp/cc52xO0c.s:8: Error: operand 1 should be an integer register -- `mov lr,x9'
> /tmp/cc52xO0c.s:7: Error: undefined symbol lr used as an immediate value
> make[2]: *** [scripts/Makefile.build:250: arch/arm64/net/bpf_jit_comp.o] Error 1
> make[1]: *** [scripts/Makefile.build:525: arch/arm64/net] Error 2
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, arm64: Fix compile error in dummy_tramp()
https://git.kernel.org/bpf/bpf-next/c/339ed900b307
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-07-21 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 12:13 [PATCH bpf-next] bpf, arm64: Fix compile error in dummy_tramp() Xu Kuohai
2022-07-21 12:45 ` Jiri Olsa
2022-07-21 13:41 ` Jean-Philippe Brucker
2022-07-21 22:30 ` patchwork-bot+netdevbpf [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=165844261408.3850.10654235868584356143.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jakub@cloudflare.com \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=will@kernel.org \
--cc=xukuohai@huaweicloud.com \
--cc=yhs@fb.com \
--cc=zlim.lnx@gmail.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