From: Stanislav Fomichev <sdf@google.com>
To: gongruiqi@huaweicloud.com
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Wang Weiyang <wangweiyang2@huawei.com>,
Xiu Jianfeng <xiujianfeng@huawei.com>,
gongruiqi1@huawei.com
Subject: Re: [PATCH] bpf: cleanup unused function declaration
Date: Fri, 2 Jun 2023 09:12:16 -0700 [thread overview]
Message-ID: <ZHoUyDMJ8xq7ENnX@google.com> (raw)
In-Reply-To: <20230602030842.279262-1-gongruiqi@huaweicloud.com>
On 06/02, GONG, Ruiqi wrote:
> All usage and the definition of `bpf_prog_free_linfo()` has been removed
> in commit e16301fbe183 ("bpf: Simplify freeing logic in linfo and
> jited_linfo"). Clean up its declaration in the header file.
>
> Signed-off-by: GONG, Ruiqi <gongruiqi@huaweicloud.com>
Acked-by: Stanislav Fomichev <sdf@google.com>
> ---
> include/linux/filter.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/filter.h b/include/linux/filter.h
> index bbce89937fde..f69114083ec7 100644
> --- a/include/linux/filter.h
> +++ b/include/linux/filter.h
> @@ -874,7 +874,6 @@ void bpf_prog_free(struct bpf_prog *fp);
>
> bool bpf_opcode_in_insntable(u8 code);
>
> -void bpf_prog_free_linfo(struct bpf_prog *prog);
> void bpf_prog_fill_jited_linfo(struct bpf_prog *prog,
> const u32 *insn_to_jit_off);
> int bpf_prog_alloc_jited_linfo(struct bpf_prog *prog);
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-06-02 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 3:08 [PATCH] bpf: cleanup unused function declaration GONG, Ruiqi
2023-06-02 16:12 ` Stanislav Fomichev [this message]
2023-06-05 23:32 ` Andrii Nakryiko
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=ZHoUyDMJ8xq7ENnX@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gongruiqi1@huawei.com \
--cc=gongruiqi@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=wangweiyang2@huawei.com \
--cc=xiujianfeng@huawei.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.