All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao1@huawei.com>
Cc: ast@kernel.org, kafai@fb.com, yhs@fb.com, daniel@iogearbox.net,
	andrii@kernel.org, zlim.lnx@gmail.com, will@kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] bpf, arm64: use emit_addr_mov_i64() for BPF_PSEUDO_FUNC
Date: Wed, 05 Jan 2022 19:50:09 +0000	[thread overview]
Message-ID: <164141220979.28548.10398527104221522201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211231151018.3781550-1-houtao1@huawei.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Fri, 31 Dec 2021 23:10:18 +0800 you wrote:
> The following error is reported when running "./test_progs -t for_each"
> under arm64:
> 
>     bpf_jit: multi-func JIT bug 58 != 56
>     ......
>     JIT doesn't support bpf-to-bpf calls
> 
> [...]

Here is the summary with links:
  - bpf, arm64: use emit_addr_mov_i64() for BPF_PSEUDO_FUNC
    https://git.kernel.org/bpf/bpf-next/c/e4a41c2c1fa9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao1@huawei.com>
Cc: ast@kernel.org, kafai@fb.com, yhs@fb.com, daniel@iogearbox.net,
	andrii@kernel.org, zlim.lnx@gmail.com, will@kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] bpf, arm64: use emit_addr_mov_i64() for BPF_PSEUDO_FUNC
Date: Wed, 05 Jan 2022 19:50:09 +0000	[thread overview]
Message-ID: <164141220979.28548.10398527104221522201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211231151018.3781550-1-houtao1@huawei.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Fri, 31 Dec 2021 23:10:18 +0800 you wrote:
> The following error is reported when running "./test_progs -t for_each"
> under arm64:
> 
>     bpf_jit: multi-func JIT bug 58 != 56
>     ......
>     JIT doesn't support bpf-to-bpf calls
> 
> [...]

Here is the summary with links:
  - bpf, arm64: use emit_addr_mov_i64() for BPF_PSEUDO_FUNC
    https://git.kernel.org/bpf/bpf-next/c/e4a41c2c1fa9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-01-05 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 15:10 [PATCH] bpf, arm64: use emit_addr_mov_i64() for BPF_PSEUDO_FUNC Hou Tao
2021-12-31 15:10 ` Hou Tao
2022-01-05 19:50 ` patchwork-bot+netdevbpf [this message]
2022-01-05 19:50   ` patchwork-bot+netdevbpf

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=164141220979.28548.10398527104221522201.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=daniel@iogearbox.net \
    --cc=houtao1@huawei.com \
    --cc=kafai@fb.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=will@kernel.org \
    --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 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.