From: patchwork-bot+netdevbpf@kernel.org
To: Xin Liu <liuxin350@huawei.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
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,
kongweibin2@huawei.com, zhangmingyi5@huawei.com
Subject: Re: [PATCH bpf-next v2] libbpf:Improved usability of the Makefile in libbpf
Date: Sat, 03 Dec 2022 00:40:15 +0000 [thread overview]
Message-ID: <167002801548.8228.2023000257620605263.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221202081738.128513-1-liuxin350@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 2 Dec 2022 16:17:38 +0800 you wrote:
> Current libbpf Makefile does not contain the help command, which
> is inconvenient to use. Similar to the Makefile help command of the
> perf, a help command is provided to list the commands supported by
> libbpf make and the functions of the commands.
>
> Signed-off-by: Xin Liu <liuxin350@huawei.com>
>
> [...]
Here is the summary with links:
- [bpf-next,v2] libbpf:Improved usability of the Makefile in libbpf
https://git.kernel.org/bpf/bpf-next/c/706819495921
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-12-03 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 8:17 [PATCH bpf-next v2] libbpf:Improved usability of the Makefile in libbpf Xin Liu
2022-12-03 0:40 ` 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=167002801548.8228.2023000257620605263.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=zhangmingyi5@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