BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@kernel.org, memxor@gmail.com, eddyz87@gmail.com,
	john.fastabend@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH v6 bpf-next 0/4] bpf: Introduce may_goto and cond_break
Date: Wed, 06 Mar 2024 18:50:29 +0000	[thread overview]
Message-ID: <170975102930.9518.8336084287032577662.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240306031929.42666-1-alexei.starovoitov@gmail.com>

Hello:

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

On Tue,  5 Mar 2024 19:19:25 -0800 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> v5 -> v6:
> - Rename BPF_JMA to BPF_JCOND
> - Addressed Andrii's review comments
> 
> v4 -> v5:
> - rewrote patch 1 to avoid fake may_goto_reg and use 'u32 may_goto_cnt' instead.
>   This way may_goto handling is similar to bpf_loop() processing.
> - fixed bug in patch 2 that RANGE_WITHIN should not use
>   rold->type == NOT_INIT as a safe signal.
> - patch 3 fixed negative offset computation in cond_break macro
> - using bpf_arena and cond_break recompiled lib/glob.c as bpf prog
>   and it works! It will be added as a selftest to arena series.
> 
> [...]

Here is the summary with links:
  - [v6,bpf-next,1/4] bpf: Introduce may_goto instruction
    https://git.kernel.org/bpf/bpf-next/c/9c4cab4e6756
  - [v6,bpf-next,2/4] bpf: Recognize that two registers are safe when their ranges match
    https://git.kernel.org/bpf/bpf-next/c/cc570d85e66e
  - [v6,bpf-next,3/4] bpf: Add cond_break macro
    https://git.kernel.org/bpf/bpf-next/c/7825948e135b
  - [v6,bpf-next,4/4] selftests/bpf: Test may_goto
    https://git.kernel.org/bpf/bpf-next/c/8089b99d4649

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



  parent reply	other threads:[~2024-03-06 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  3:19 [PATCH v6 bpf-next 0/4] bpf: Introduce may_goto and cond_break Alexei Starovoitov
2024-03-06  3:19 ` [PATCH v6 bpf-next 1/4] bpf: Introduce may_goto instruction Alexei Starovoitov
2024-03-06 13:12   ` Eduard Zingerman
2024-03-06 16:40     ` Alexei Starovoitov
2024-03-06 18:33   ` Andrii Nakryiko
2024-03-06 18:38     ` Alexei Starovoitov
2024-03-06  3:19 ` [PATCH v6 bpf-next 2/4] bpf: Recognize that two registers are safe when their ranges match Alexei Starovoitov
2024-03-06 13:07   ` Eduard Zingerman
2024-03-06  3:19 ` [PATCH v6 bpf-next 3/4] bpf: Add cond_break macro Alexei Starovoitov
2024-03-06 13:26   ` Eduard Zingerman
2024-03-06 16:51     ` Alexei Starovoitov
2024-03-06  3:19 ` [PATCH v6 bpf-next 4/4] selftests/bpf: Test may_goto Alexei Starovoitov
2024-03-06 18:50 ` patchwork-bot+netdevbpf [this message]
2024-03-06 19:15   ` [PATCH v6 bpf-next 0/4] bpf: Introduce may_goto and cond_break John Fastabend

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=170975102930.9518.8336084287032577662.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.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