BPF List
 help / color / mirror / Atom feed
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 v2 bpf-next 0/2] fixes for bpf_prog_pack
Date: Wed, 02 Mar 2022 21:30:10 +0000	[thread overview]
Message-ID: <164625661080.14464.1524494677053022306.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220302175126.247459-1-song@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 2 Mar 2022 09:51:24 -0800 you wrote:
> Changes v1 => v2:
> 1. Rephrase comments in 2/2. (Yonghong)
> 
> Two fixes for bpf_prog_pack.
> 
> Song Liu (2):
>   x86: disable HAVE_ARCH_HUGE_VMALLOC on 32-bit x86
>   bpf, x86: set header->size properly before freeing it
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/2] x86: disable HAVE_ARCH_HUGE_VMALLOC on 32-bit x86
    https://git.kernel.org/bpf/bpf-next/c/eed1fcee556f
  - [v2,bpf-next,2/2] bpf, x86: set header->size properly before freeing it
    https://git.kernel.org/bpf/bpf-next/c/676b2daabaf9

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



      parent reply	other threads:[~2022-03-02 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 17:51 [PATCH v2 bpf-next 0/2] fixes for bpf_prog_pack Song Liu
2022-03-02 17:51 ` [PATCH v2 bpf-next 1/2] x86: disable HAVE_ARCH_HUGE_VMALLOC on 32-bit x86 Song Liu
2022-03-02 17:51 ` [PATCH v2 bpf-next 2/2] bpf, x86: set header->size properly before freeing it Song Liu
2022-03-02 21: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=164625661080.14464.1524494677053022306.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