From: patchwork-bot+netdevbpf@kernel.org
To: Daniel T. Lee <danieltimlee@gmail.com>
Cc: daniel@iogearbox.net, ast@kernel.org, andrii.nakryiko@gmail.com,
john.fastabend@gmail.com, sdf@google.com, kpsingh@kernel.org,
yhs@fb.com, song@kernel.org, martin.lau@linux.dev,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: replace open code with for allocated object check
Date: Mon, 05 Jun 2023 21:40:20 +0000 [thread overview]
Message-ID: <168600122068.24826.11624326531846760051.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230527122706.59315-1-danieltimlee@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 27 May 2023 21:27:06 +0900 you wrote:
> From commit 282de143ead9 ("bpf: Introduce allocated objects support"),
> With this allocated object with BPF program, (PTR_TO_BTF_ID | MEM_ALLOC)
> has been a way of indicating to check the type is the allocated object.
>
> commit d8939cb0a03c ("bpf: Loosen alloc obj test in verifier's
> reg_btf_record")
> From the commit, there has been helper function for checking this, named
> type_is_ptr_alloc_obj(). But still, some of the code use open code to
> retrieve this info. This commit replaces the open code with the
> type_is_alloc(), and the type_is_ptr_alloc_obj() function.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: replace open code with for allocated object check
https://git.kernel.org/bpf/bpf-next/c/503e4def5414
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-06-05 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 12:27 [PATCH bpf-next] bpf: replace open code with for allocated object check Daniel T. Lee
2023-06-05 21:40 ` 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=168600122068.24826.11624326531846760051.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=danieltimlee@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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