public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, kernel-team@fb.com, yhs@fb.com,
	memxor@gmail.com
Subject: Re: [PATCH v5 bpf-next 1/4] bpf: Allow ringbuf memory to be used as map key
Date: Sat, 22 Oct 2022 02:30:19 +0000	[thread overview]
Message-ID: <166640581979.9082.14191234166274787215.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221020160721.4030492-1-davemarchevsky@fb.com>

Hello:

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

On Thu, 20 Oct 2022 09:07:18 -0700 you wrote:
> This patch adds support for the following pattern:
> 
>   struct some_data *data = bpf_ringbuf_reserve(&ringbuf, sizeof(struct some_data, 0));
>   if (!data)
>     return;
>   bpf_map_lookup_elem(&another_map, &data->some_field);
>   bpf_ringbuf_submit(data);
> 
> [...]

Here is the summary with links:
  - [v5,bpf-next,1/4] bpf: Allow ringbuf memory to be used as map key
    https://git.kernel.org/bpf/bpf-next/c/9ef40974a82a
  - [v5,bpf-next,2/4] bpf: Consider all mem_types compatible for map_{key,value} args
    https://git.kernel.org/bpf/bpf-next/c/d1673304097c
  - [v5,bpf-next,3/4] selftests/bpf: Add test verifying bpf_ringbuf_reserve retval use in map ops
    https://git.kernel.org/bpf/bpf-next/c/51ee71d38d8c
  - [v5,bpf-next,4/4] selftests/bpf: Add write to hashmap to array_map iter test
    https://git.kernel.org/bpf/bpf-next/c/8f4bc15b9ad7

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-22  2:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 16:07 [PATCH v5 bpf-next 1/4] bpf: Allow ringbuf memory to be used as map key Dave Marchevsky
2022-10-20 16:07 ` [PATCH v5 bpf-next 2/4] bpf: Consider all mem_types compatible for map_{key,value} args Dave Marchevsky
2022-10-21 23:04   ` Andrii Nakryiko
2022-10-22  2:26     ` Alexei Starovoitov
2022-10-20 16:07 ` [PATCH v5 bpf-next 3/4] selftests/bpf: Add test verifying bpf_ringbuf_reserve retval use in map ops Dave Marchevsky
2022-10-21 23:04   ` Andrii Nakryiko
2022-10-20 16:07 ` [PATCH v5 bpf-next 4/4] selftests/bpf: Add write to hashmap to array_map iter test Dave Marchevsky
2022-10-21 23:04   ` Andrii Nakryiko
2022-10-21 23:04 ` [PATCH v5 bpf-next 1/4] bpf: Allow ringbuf memory to be used as map key Andrii Nakryiko
2022-10-22  2:30 ` 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=166640581979.9082.14191234166274787215.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=davemarchevsky@fb.com \
    --cc=kernel-team@fb.com \
    --cc=memxor@gmail.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