From: patchwork-bot+netdevbpf@kernel.org
To: Ruiqi Gong <gongruiqi@huaweicloud.com>
Cc: andrii.nakryiko@gmail.com, sdf@google.com, ast@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com,
martin.lau@linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, wangweiyang2@huawei.com,
xiujianfeng@huawei.com, gongruiqi1@huawei.com
Subject: Re: [PATCH RESEND] bpf: cleanup unused function declaration
Date: Tue, 06 Jun 2023 15:10:20 +0000 [thread overview]
Message-ID: <168606422036.10567.7750110941195035658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230606021047.170667-1-gongruiqi@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 6 Jun 2023 10:10:47 +0800 you 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: Ruiqi Gong <gongruiqi@huaweicloud.com>
> Acked-by: Stanislav Fomichev <sdf@google.com>
> Link: https://lore.kernel.org/all/20230602030842.279262-1-gongruiqi@huaweicloud.com/
>
> [...]
Here is the summary with links:
- [RESEND] bpf: cleanup unused function declaration
https://git.kernel.org/bpf/bpf-next/c/aa6182707a53
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:[~2023-06-06 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 2:10 [PATCH RESEND] bpf: cleanup unused function declaration Ruiqi Gong
2023-06-06 15:10 ` 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=168606422036.10567.7750110941195035658.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--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=sdf@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox