From: patchwork-bot+netdevbpf@kernel.org
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org, linux-mm@kvack.org,
root@localhost.localdomain
Subject: Re: [PATCH bpf-next 0/2] bpf: MM related minor changes
Date: Sun, 19 Oct 2025 02:30:14 +0000 [thread overview]
Message-ID: <176084101401.3155740.15408477033569481420.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251016063929.13830-1-laoar.shao@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 16 Oct 2025 14:39:27 +0800 you wrote:
> From: root <root@localhost.localdomain>
>
> These two minor patches were developed during the implementation of
> BPF-THP:
>
> https://lwn.net/Articles/1042138/
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: mark mm->owner as __safe_rcu_or_null
https://git.kernel.org/bpf/bpf-next/c/ec8e3e27a140
- [bpf-next,2/2] bpf: mark vma->{vm_mm,vm_file} as __safe_trusted_or_null
https://git.kernel.org/bpf/bpf-next/c/7484e7cd8ab1
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:[~2025-10-19 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 6:39 [PATCH bpf-next 0/2] bpf: MM related minor changes Yafang Shao
2025-10-16 6:39 ` [PATCH bpf-next 1/2] bpf: mark mm->owner as __safe_rcu_or_null Yafang Shao
2025-10-16 6:39 ` [PATCH bpf-next 2/2] bpf: mark vma->{vm_mm,vm_file} as __safe_trusted_or_null Yafang Shao
2025-10-16 16:56 ` [PATCH bpf-next 0/2] bpf: MM related minor changes Song Liu
2025-10-19 2: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=176084101401.3155740.15408477033569481420.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=martin.lau@linux.dev \
--cc=root@localhost.localdomain \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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