From: patchwork-bot+bpf@kernel.org
To: =?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci.codeaurora.org
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf_iter: don't fail test due to missing __builtin_btf_type_id
Date: Tue, 29 Sep 2020 18:30:02 +0000 [thread overview]
Message-ID: <160140420265.22687.13555607329686499231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200929123004.46694-1-toke@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 29 Sep 2020 14:30:04 +0200 you wrote:
> The new test for task iteration in bpf_iter checks (in do_btf_read()) if it
> should be skipped due to missing __builtin_btf_type_id. However, this
> 'skip' verdict is not propagated to the caller, so the parent test will
> still fail. Fix this by also skipping the rest of the parent test if the
> skip condition was reached.
>
> Fixes: b72091bd4ee4 ("selftests/bpf: Add test for bpf_seq_printf_btf helper")
> Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf_iter: don't fail test due to missing __builtin_btf_type_id
https://git.kernel.org/bpf/bpf-next/c/d2197c7ff171
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:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 12:30 [PATCH bpf-next] selftests/bpf_iter: don't fail test due to missing __builtin_btf_type_id Toke Høiland-Jørgensen
2020-09-29 12:35 ` Alan Maguire
2020-09-29 12:50 ` Toke Høiland-Jørgensen
2020-09-29 18:30 ` 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=160140420265.22687.13555607329686499231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bpf@kernel.org \
--cc==?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci.codeaurora.org \
--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