From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@meta.com
Subject: Re: [PATCH bpf] selftests/bpf: Adjust btf_dump test to reflect recent change in file_operations
Date: Fri, 17 May 2024 00:00:31 +0000 [thread overview]
Message-ID: <171590403160.16758.17938895621853444532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240516164310.2481460-1-martin.lau@linux.dev>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 16 May 2024 09:43:10 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> The btf_dump test fails:
>
> test_btf_dump_struct_data:FAIL:file_operations unexpected file_operations: actual '(struct file_operations){
> .owner = (struct module *)0xffffffffffffffff,
> .fop_flags = (fop_flags_t)4294967295,
> .llseek = (loff_t (*)(struct f' != expected '(struct file_operations){
> .owner = (struct module *)0xffffffffffffffff,
> .llseek = (loff_t (*)(struct file *, loff_t, int))0xffffffffffffffff,'
>
> [...]
Here is the summary with links:
- [bpf] selftests/bpf: Adjust btf_dump test to reflect recent change in file_operations
https://git.kernel.org/bpf/bpf/c/51e2b8d33199
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:[~2024-05-17 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 16:43 [PATCH bpf] selftests/bpf: Adjust btf_dump test to reflect recent change in file_operations Martin KaFai Lau
2024-05-16 16:54 ` Alan Maguire
2024-05-17 0: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=171590403160.16758.17938895621853444532.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=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
/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.