From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
john.fastabend@gmail.com, xrivendell7@gmail.com,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next v3 0/2] bpf: Use GFP_KERNEL in bpf_event_entry_gen()
Date: Thu, 14 Dec 2023 05:10:25 +0000 [thread overview]
Message-ID: <170253062594.9483.485230140941788020.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231214043010.3458072-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 14 Dec 2023 12:30:08 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> The simple patch set aims to replace GFP_ATOMIC by GFP_KERNEL in
> bpf_event_entry_gen(). These two patches in the patch set were
> preparatory patches in "Fix the release of inner map" patchset [1] and
> are not needed for v2, so re-post it to bpf-next tree.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Reduce the scope of rcu_read_lock when updating fd map
https://git.kernel.org/bpf/bpf-next/c/8f82583f9527
- [bpf-next,v3,2/2] bpf: Use GFP_KERNEL in bpf_event_entry_gen()
https://git.kernel.org/bpf/bpf-next/c/dc68540913ac
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-14 5:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 4:30 [PATCH bpf-next v3 0/2] bpf: Use GFP_KERNEL in bpf_event_entry_gen() Hou Tao
2023-12-14 4:30 ` [PATCH bpf-next v3 1/2] bpf: Reduce the scope of rcu_read_lock when updating fd map Hou Tao
2023-12-14 6:22 ` John Fastabend
2023-12-14 7:31 ` Hou Tao
2023-12-14 13:55 ` Alexei Starovoitov
2023-12-14 19:15 ` John Fastabend
2023-12-15 3:23 ` Alexei Starovoitov
2023-12-15 3:39 ` Hou Tao
2023-12-15 8:18 ` Hou Tao
2023-12-14 4:30 ` [PATCH bpf-next v3 2/2] bpf: Use GFP_KERNEL in bpf_event_entry_gen() Hou Tao
2023-12-14 5:10 ` 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=170253062594.9483.485230140941788020.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=xrivendell7@gmail.com \
--cc=yonghong.song@linux.dev \
/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