BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix bpftool synctypes checking failure
Date: Wed, 26 Oct 2022 17:10:15 +0000	[thread overview]
Message-ID: <166680421579.6635.1102994754514154034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221026163014.470732-1-yhs@fb.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 26 Oct 2022 09:30:14 -0700 you wrote:
> kernel-patches/bpf failed with error:
>   Running bpftool checks...
>   Comparing /data/users/ast/net-next/tools/include/uapi/linux/bpf.h (bpf_map_type) and
>             /data/users/ast/net-next/tools/bpf/bpftool/map.c (do_help() TYPE):
>             {'cgroup_storage_deprecated', 'cgroup_storage'}
>   Comparing /data/users/ast/net-next/tools/include/uapi/linux/bpf.h (bpf_map_type) and
>             /data/users/ast/net-next/tools/bpf/bpftool/Documentation/bpftool-map.rst (TYPE):
>             {'cgroup_storage_deprecated', 'cgroup_storage'}
> The selftests/bpf/test_bpftool_synctypes.py runs checking in the above.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix bpftool synctypes checking failure
    https://git.kernel.org/bpf/bpf-next/c/d96d4276eaeb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-10-26 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 16:30 [PATCH bpf-next] selftests/bpf: Fix bpftool synctypes checking failure Yonghong Song
2022-10-26 17:01 ` Quentin Monnet
2022-10-26 17:10 ` 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=166680421579.6635.1102994754514154034.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@fb.com \
    --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