From: Martin KaFai Lau <kafai@fb.com>
To: grantseltzer <grantseltzer@gmail.com>
Cc: <andrii@kernel.org>, <daniel@iogearbox.net>,
<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: Mon, 22 Feb 2021 14:00:17 -0800 [thread overview]
Message-ID: <20210222220017.qw3fby6mapnveg3u@kafai-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210222195846.155483-1-grantseltzer@gmail.com>
On Mon, Feb 22, 2021 at 07:58:46PM +0000, grantseltzer 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.
Acked-by: Martin KaFai Lau <kafai@fb.com>
[ Acked-by and Reviewed-by can be carried over to
the following revisions if the change is obvious.
Also, it is useful to comment on what has
changed between revisions. There is no need
to resend this patch just for this though. ]
next prev parent reply other threads:[~2021-02-22 22:01 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 [this message]
2021-02-23 6:37 ` Andrii Nakryiko
2021-02-23 6:41 ` patchwork-bot+netdevbpf
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=20210222220017.qw3fby6mapnveg3u@kafai-mbp.dhcp.thefacebook.com \
--to=kafai@fb.com \
--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=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).