From: patchwork-bot+netdevbpf@kernel.org
To: Peilin Ye <yepeilin.cs@gmail.com>
Cc: martin.lau@linux.dev, peilin.ye@bytedance.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf/btf: Use btf_type_str() whenever possible
Date: Sat, 17 Sep 2022 00:30:15 +0000 [thread overview]
Message-ID: <166337461521.10363.5012920273929105256.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220916202800.31421-1-yepeilin.cs@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Fri, 16 Sep 2022 13:28:00 -0700 you wrote:
> From: Peilin Ye <peilin.ye@bytedance.com>
>
> We have btf_type_str(). Use it whenever possible in btf.c, instead of
> "btf_kind_str[BTF_INFO_KIND(t->info)]".
>
> Signed-off-by: Peilin Ye <peilin.ye@bytedance.com>
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf/btf: Use btf_type_str() whenever possible
https://git.kernel.org/bpf/bpf-next/c/571f9738bfb3
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-09-17 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 2:13 [PATCH bpf-next] bpf/btf: Use btf_type_str() whenever possible Peilin Ye
2022-09-16 18:37 ` Martin KaFai Lau
2022-09-16 20:26 ` Peilin Ye
2022-09-16 20:28 ` [PATCH bpf-next v2] " Peilin Ye
2022-09-17 0: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=166337461521.10363.5012920273929105256.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=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=peilin.ye@bytedance.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yepeilin.cs@gmail.com \
--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