From: patchwork-bot+netdevbpf@kernel.org
To: Grant Seltzer Richman <grantseltzer@gmail.com>
Cc: andrii@kernel.org, daniel@iogearbox.net, kafai@fb.com,
songliubraving@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, irogers@google.com, yhs@fb.com,
tklauser@distanz.ch, netdev@vger.kernel.org,
mrostecki@opensuse.org, ast@kernel.org, quentin@isovalent.com,
bpf@vger.kernel.org
Subject: Re: [PATCH v4 bpf-next] Add CONFIG_DEBUG_INFO_BTF and CONFIG_DEBUG_INFO_BTF_MODULES check to bpftool feature command
Date: Tue, 23 Feb 2021 06:41:14 +0000 [thread overview]
Message-ID: <161406247460.885.4219717634423905912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210222195846.155483-1-grantseltzer@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 22 Feb 2021 19:58:46 +0000 you wrote:
> This adds both the CONFIG_DEBUG_INFO_BTF and CONFIG_DEBUG_INFO_BTF_MODULES
> kernel compile option to output of the bpftool feature command.
> This is relevant for developers that want to account for data structure
> definition differences between kernels.
>
> Signed-off-by: Grant Seltzer <grantseltzer@gmail.com>
>
> [...]
Here is the summary with links:
- [v4,bpf-next] Add CONFIG_DEBUG_INFO_BTF and CONFIG_DEBUG_INFO_BTF_MODULES check to bpftool feature command
https://git.kernel.org/bpf/bpf-next/c/6b12bb20aeb3
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:[~2021-02-23 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 19:58 [PATCH v4 bpf-next] Add CONFIG_DEBUG_INFO_BTF and CONFIG_DEBUG_INFO_BTF_MODULES check to bpftool feature command grantseltzer
2021-02-22 22:00 ` Martin KaFai Lau
2021-02-23 6:37 ` Andrii Nakryiko
2021-02-23 6:41 ` 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=161406247460.885.4219717634423905912.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=grantseltzer@gmail.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=mrostecki@opensuse.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@fb.com \
--cc=tklauser@distanz.ch \
--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;
as well as URLs for NNTP newsgroup(s).