From: Stanislav Fomichev <sdf@google.com>
To: Wenli Xie <xwlpt@126.com>
Cc: martin.lau@linux.dev, ast@kernel.org, daniel@iogearbox.net,
song@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, Wenli Xie <wlxie7296@gmail.com>
Subject: Re: [PATCH] bpf: Get the program type by resolve_prog_type() directly
Date: Mon, 13 Nov 2023 06:15:12 -0800 [thread overview]
Message-ID: <ZVIvcM3BDOvKGpwa@google.com> (raw)
In-Reply-To: <20231113031812.3639430-1-xwlpt@126.com>
On 11/13, Wenli Xie wrote:
> From: Wenli Xie <wlxie7296@gmail.com>
>
> The bpf program type can be get by resolve_prog_type() directly.
Can we have more details in the change log about why using
resolve_prog_type is better?
Please also take a look at Documentation/bpf/bpf_devel_QA.rst on
how to target the right tree ([PATCH bpf-next]).
prev parent reply other threads:[~2023-11-13 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 3:18 [PATCH] bpf: Get the program type by resolve_prog_type() directly Wenli Xie
2023-11-13 14:15 ` Stanislav Fomichev [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=ZVIvcM3BDOvKGpwa@google.com \
--to=sdf@google.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=wlxie7296@gmail.com \
--cc=xwlpt@126.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.