BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, yhs@fb.com,
	alan.maguire@oracle.com
Subject: Re: [PATCH bpf-next 1/2] libbpf: Resolve enum fwd as full enum64 and vice versa
Date: Fri, 04 Nov 2022 20:20:15 +0000	[thread overview]
Message-ID: <166759321505.8776.1021581252608507513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221101235413.1824260-1-eddyz87@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed,  2 Nov 2022 01:54:12 +0200 you wrote:
> Changes de-duplication logic for enums in the following way:
> - update btf_hash_enum to ignore size and kind fields to get
>   ENUM and ENUM64 types in a same hash bucket;
> - update btf_compat_enum to consider enum fwd to be compatible with
>   full enum64 (and vice versa);
> 
> This allows BTF de-duplication in the following case:
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] libbpf: Resolve enum fwd as full enum64 and vice versa
    https://git.kernel.org/bpf/bpf-next/c/de048b6ee865
  - [bpf-next,2/2] selftests/bpf: Tests for enum fwd resolved as full enum64
    https://git.kernel.org/bpf/bpf-next/c/2e20f50ff849

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-11-04 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 23:54 [PATCH bpf-next 1/2] libbpf: Resolve enum fwd as full enum64 and vice versa Eduard Zingerman
2022-11-01 23:54 ` [PATCH bpf-next 2/2] selftests/bpf: Tests for enum fwd resolved as full enum64 Eduard Zingerman
2022-11-04 20: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=166759321505.8776.1021581252608507513.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --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