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] fix bpf_prog_pack build errors
Date: Wed, 09 Feb 2022 05:20:25 +0000 [thread overview]
Message-ID: <164438402548.12376.6829583277073012575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220208220509.4180389-1-song@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 8 Feb 2022 14:05:07 -0800 you wrote:
> Fix build errors reported by kernel test robot.
>
> Song Liu (2):
> bpf: fix leftover header->pages in sparc and powerpc code.
> bpf: fix bpf_prog_pack build HPAGE_PMD_SIZE
>
> arch/powerpc/net/bpf_jit_comp.c | 2 +-
> arch/sparc/net/bpf_jit_comp_64.c | 2 +-
> kernel/bpf/core.c | 4 ++++
> 3 files changed, 6 insertions(+), 2 deletions(-)
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: fix leftover header->pages in sparc and powerpc code.
https://git.kernel.org/bpf/bpf-next/c/0f350231b5ac
- [bpf-next,2/2] bpf: fix bpf_prog_pack build HPAGE_PMD_SIZE
https://git.kernel.org/bpf/bpf-next/c/c1b13a9451ab
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-02-09 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 22:05 [PATCH bpf-next 0/2] fix bpf_prog_pack build errors Song Liu
2022-02-08 22:05 ` [PATCH bpf-next 1/2] bpf: fix leftover header->pages in sparc and powerpc code Song Liu
2022-02-08 22:05 ` [PATCH bpf-next 2/2] bpf: fix bpf_prog_pack build HPAGE_PMD_SIZE Song Liu
2022-02-10 1:13 ` Eric Dumazet
2022-02-10 5:59 ` Song Liu
2022-02-09 5:20 ` 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=164438402548.12376.6829583277073012575.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 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.