From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/2] fixes for bpf_prog_pack
Date: Mon, 21 Mar 2022 21:00:10 +0000 [thread overview]
Message-ID: <164789641078.12886.8468813279524303384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220321180009.1944482-1-song@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 21 Mar 2022 11:00:07 -0700 you wrote:
> Two fixes for issues reported by syzbot and kernel test robot.
>
> Song Liu (2):
> bpf: fix bpf_prog_pack for multi-node setup
> bpf: fix bpf_prog_pack when PMU_SIZE is not defined
>
> kernel/bpf/core.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: fix bpf_prog_pack for multi-node setup
https://git.kernel.org/bpf/bpf-next/c/96805674e562
- [bpf-next,2/2] bpf: fix bpf_prog_pack when PMU_SIZE is not defined
https://git.kernel.org/bpf/bpf-next/c/e581094167be
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-03-21 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 18:00 [PATCH bpf-next 0/2] fixes for bpf_prog_pack Song Liu
2022-03-21 18:00 ` [PATCH bpf-next 1/2] bpf: fix bpf_prog_pack for multi-node setup Song Liu
2022-03-21 18:00 ` [PATCH bpf-next 2/2] bpf: fix bpf_prog_pack when PMU_SIZE is not defined Song Liu
2022-03-21 21:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-02 0:43 [PATCH bpf-next 0/2] fixes for bpf_prog_pack Song Liu
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=164789641078.12886.8468813279524303384.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=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=song@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox