From: patchwork-bot+netdevbpf@kernel.org
To: Changbin Du <changbin.du@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
quentin@isovalent.com, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, shuah@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, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
mykolal@fb.com, linux-perf-users@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/2] bpftool: improve error handing for missing .BTF section
Date: Wed, 21 Dec 2022 00:20:15 +0000 [thread overview]
Message-ID: <167158201594.10746.1700906742257656233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221217223509.88254-1-changbin.du@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sun, 18 Dec 2022 06:35:07 +0800 you wrote:
> Display error message for missing ".BTF" section and clean up empty
> vmlinux.h file.
>
> v3:
> - fix typo and make error message consistent. (Andrii Nakryiko)
> - split out perf change.
> v2:
> - remove vmlinux specific error info.
> - use builtin target .DELETE_ON_ERROR: to delete empty vmlinux.h
>
> [...]
Here is the summary with links:
- [v3,1/2] libbpf: show error info about missing ".BTF" section
https://git.kernel.org/bpf/bpf-next/c/e6b4e1d759d3
- [v3,2/2] bpf: makefiles: do not generate empty vmlinux.h
https://git.kernel.org/bpf/bpf-next/c/e7f0d5cdd023
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-21 0:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 22:35 [PATCH v3 0/2] bpftool: improve error handing for missing .BTF section Changbin Du
2022-12-17 22:35 ` [PATCH v3 1/2] libbpf: show error info about missing ".BTF" section Changbin Du
2022-12-19 3:45 ` Leo Yan
2022-12-20 1:31 ` Changbin Du
2022-12-20 11:34 ` Leo Yan
2022-12-21 0:13 ` Andrii Nakryiko
2022-12-21 3:55 ` Leo Yan
2022-12-22 18:51 ` Andrii Nakryiko
2022-12-30 12:10 ` Changbin Du
2022-12-30 12:28 ` Leo Yan
2023-01-03 15:03 ` Quentin Monnet
2023-01-03 23:46 ` Andrii Nakryiko
2023-01-05 14:57 ` Quentin Monnet
2022-12-17 22:35 ` [PATCH v3 2/2] bpf: makefiles: do not generate empty vmlinux.h Changbin Du
2022-12-19 3:59 ` Leo Yan
2022-12-20 1:26 ` Changbin Du
2022-12-20 15:38 ` Quentin Monnet
2022-12-21 0:20 ` 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=167158201594.10746.1700906742257656233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changbin.du@gmail.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=mykolal@fb.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).