From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com, xukuohai@huawei.com,
will@kernel.org, nathan@kernel.org, pulehui@huawei.com,
bjorn@kernel.org, iii@linux.ibm.com, lee@kernel.org
Subject: Re: [PATCHv4 bpf 0/2] bpf: Fix map poke update
Date: Wed, 06 Dec 2023 21:50:24 +0000 [thread overview]
Message-ID: <170189942405.8360.841119642770119947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206083041.1306660-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 6 Dec 2023 09:30:39 +0100 you wrote:
> hi,
> this patchset fixes the issue reported in [0].
>
> v4 changes:
> - added missing bpf_arch_poke_desc_update prototype [lkp]
> - added comments to the test
> - moved the test under prog_tests/tailcalls.c
>
> [...]
Here is the summary with links:
- [PATCHv4,bpf,1/2] bpf: Fix prog_array_map_poke_run map poke update
https://git.kernel.org/bpf/bpf/c/4b7de801606e
- [PATCHv4,bpf,2/2] selftests/bpf: Add test for early update in prog_array_map_poke_run
https://git.kernel.org/bpf/bpf/c/ffed24eff9e0
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:[~2023-12-06 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 8:30 [PATCHv4 bpf 0/2] bpf: Fix map poke update Jiri Olsa
2023-12-06 8:30 ` [PATCHv4 bpf 1/2] bpf: Fix prog_array_map_poke_run " Jiri Olsa
2023-12-21 9:07 ` Lee Jones
2023-12-21 9:34 ` Greg KH
2023-12-21 9:55 ` Lee Jones
2023-12-21 10:02 ` Greg KH
2023-12-21 10:17 ` Lee Jones
2023-12-21 14:00 ` Jiri Olsa
2023-12-21 14:34 ` Lee Jones
2023-12-06 8:30 ` [PATCHv4 bpf 2/2] selftests/bpf: Add test for early update in prog_array_map_poke_run Jiri Olsa
2023-12-06 21:50 ` 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=170189942405.8360.841119642770119947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=lee@kernel.org \
--cc=nathan@kernel.org \
--cc=pulehui@huawei.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=will@kernel.org \
--cc=xukuohai@huawei.com \
--cc=yhs@fb.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