From: patchwork-bot+bpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] selftests/bpf: BTF-based kernel data display fixes
Date: Tue, 29 Sep 2020 18:20:03 +0000 [thread overview]
Message-ID: <160140360303.18925.12949460606105895151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1601379151-21449-1-git-send-email-alan.maguire@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 29 Sep 2020 04:32:29 -0700 (PDT) you wrote:
> Resolve issues in bpf selftests introduced with BTF-based kernel data
> display selftests; these are
>
> - a warning introduced in snprintf_btf.c; and
> - compilation failures with old kernels vmlinux.h
>
> Alan Maguire (2):
> selftests/bpf: fix unused-result warning in snprintf_btf.c
> selftests/bpf: ensure snprintf_btf/bpf_iter tests compatibility with
> old vmlinux.h
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] selftests/bpf: fix unused-result warning in snprintf_btf.c
https://git.kernel.org/bpf/bpf-next/c/96c48058db15
- [bpf-next,2/2] selftests/bpf: ensure snprintf_btf/bpf_iter tests compatibility with old vmlinux.h
https://git.kernel.org/bpf/bpf-next/c/cfe77683b8d4
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:[~2020-09-29 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 11:32 [PATCH bpf-next 0/2] selftests/bpf: BTF-based kernel data display fixes Alan Maguire
2020-09-29 11:32 ` [PATCH bpf-next 1/2] selftests/bpf: fix unused-result warning in snprintf_btf.c Alan Maguire
2020-09-29 11:32 ` [PATCH bpf-next 2/2] selftests/bpf: ensure snprintf_btf/bpf_iter tests compatibility with old vmlinux.h Alan Maguire
2020-09-29 18:08 ` Andrii Nakryiko
2020-09-29 18:20 ` patchwork-bot+bpf [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=160140360303.18925.12949460606105895151.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
/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).