All of lore.kernel.org
 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, acme@kernel.org
Subject: Re: [PATCH bpf-next v4 0/3] libbpf: Resolve unambigous forward declarations
Date: Thu, 10 Nov 2022 05:00:16 +0000	[thread overview]
Message-ID: <166805641643.4596.8079204594664124141.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109142611.879983-1-eddyz87@gmail.com>

Hello:

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

On Wed,  9 Nov 2022 16:26:08 +0200 you wrote:
> The patch-set is consists of the following parts:
> - An update for libbpf's hashmap interface from void* -> void* to a
>   polymorphic one, allowing to use both long and void* keys and values
>   w/o additional casts. Interface functions are hidden behind
>   auxiliary macro that add casts as necessary.
> 
>   This simplifies many use cases in libbpf as hashmaps there are
>   mostly integer to integer and required awkward looking incantations
>   like `(void *)(long)off` previously. Also includes updates for perf
>   as it copies map implementation from libbpf.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/3] libbpf: hashmap interface update to allow both long and void* keys/values
    https://git.kernel.org/bpf/bpf-next/c/c302378bc157
  - [bpf-next,v4,2/3] libbpf: Resolve unambigous forward declarations
    https://git.kernel.org/bpf/bpf-next/c/082108fd6932
  - [bpf-next,v4,3/3] selftests/bpf: Tests for btf_dedup_resolve_fwds
    https://git.kernel.org/bpf/bpf-next/c/99e18fad5ff7

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-10  5:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 14:26 [PATCH bpf-next v4 0/3] libbpf: Resolve unambigous forward declarations Eduard Zingerman
2022-11-09 14:26 ` [PATCH bpf-next v4 1/3] libbpf: hashmap interface update to allow both long and void* keys/values Eduard Zingerman
2022-11-10  4:54   ` Andrii Nakryiko
2022-11-10 12:28     ` Eduard Zingerman
2022-11-11 18:20       ` Andrii Nakryiko
2022-11-09 14:26 ` [PATCH bpf-next v4 2/3] libbpf: Resolve unambigous forward declarations Eduard Zingerman
2022-11-09 14:26 ` [PATCH bpf-next v4 3/3] selftests/bpf: Tests for btf_dedup_resolve_fwds Eduard Zingerman
2022-11-10  5: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=166805641643.4596.8079204594664124141.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=acme@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 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.