From: patchwork-bot+netdevbpf@kernel.org
To: Xin Liu <liuxin350@huawei.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, yanan@huawei.com,
wuchangye@huawei.com, xiesongyang@huawei.com, zhudi2@huawei.com,
kongweibin2@huawei.com
Subject: Re: [PATCH v3] libbpf: Clean up legacy bpf maps declaration in bpf_helpers
Date: Fri, 16 Sep 2022 21:00:17 +0000 [thread overview]
Message-ID: <166336201710.13694.6117441685793027381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220913073643.19960-1-liuxin350@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 13 Sep 2022 15:36:43 +0800 you wrote:
> Legacy bpf maps declaration were no longer supported in Libbpf 1.0.
> So it was time to remove the definition of bpf_map_def in bpf_helpers.h.
> Supported in Libbpf 1.0 ([0])
>
> [0]:https://github.com/libbpf/libbpf/wiki/Libbpf:-the-road-to-v1.0
>
> Acked-by: Song Liu <song@kernel.org>
> Signed-off-by: Xin Liu <liuxin350@huawei.com>
>
> [...]
Here is the summary with links:
- [v3] libbpf: Clean up legacy bpf maps declaration in bpf_helpers
https://git.kernel.org/bpf/bpf-next/c/dc567045f159
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:[~2022-09-16 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 7:36 [PATCH v3] libbpf: Clean up legacy bpf maps declaration in bpf_helpers Xin Liu
2022-09-16 21:00 ` 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=166336201710.13694.6117441685793027381.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kongweibin2@huawei.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxin350@huawei.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=yhs@fb.com \
--cc=zhudi2@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.