BPF Archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Cupertino Miranda <cupertino.miranda@oracle.com>
Cc: bpf@vger.kernel.org, yonghong.song@linux.dev,
	alexei.starovoitov@gmail.com, david.faust@oracle.com,
	jose.marchesi@oracle.com, elena.zannoni@oracle.com,
	eddyz87@gmail.com, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v5 0/6] bpf/verifier: range computation improvements
Date: Tue, 07 May 2024 00:20:28 +0000	[thread overview]
Message-ID: <171504122871.27463.1368138144281847004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240506141849.185293-1-cupertino.miranda@oracle.com>

Hello:

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

On Mon,  6 May 2024 15:18:43 +0100 you wrote:
> Hi everyone,
> 
> This is what I hope to be the last version. :)
> 
> Regards,
> Cupertino
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/6] bpf/verifier: replace calls to mark_reg_unknown.
    https://git.kernel.org/bpf/bpf-next/c/d786957ebd3f
  - [bpf-next,v5,2/6] bpf/verifier: refactor checks for range computation
    https://git.kernel.org/bpf/bpf-next/c/0922c78f592c
  - [bpf-next,v5,3/6] bpf/verifier: improve XOR and OR range computation
    https://git.kernel.org/bpf/bpf-next/c/138cc42c05d1
  - [bpf-next,v5,4/6] selftests/bpf: XOR and OR range computation tests.
    https://git.kernel.org/bpf/bpf-next/c/5ec9a7d13f49
  - [bpf-next,v5,5/6] bpf/verifier: relax MUL range computation check
    https://git.kernel.org/bpf/bpf-next/c/41d047a87106
  - [bpf-next,v5,6/6] selftests/bpf: MUL range computation tests.
    https://git.kernel.org/bpf/bpf-next/c/92956786b4e2

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-05-07  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 14:18 [PATCH bpf-next v5 0/6] bpf/verifier: range computation improvements Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 1/6] bpf/verifier: replace calls to mark_reg_unknown Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 2/6] bpf/verifier: refactor checks for range computation Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 3/6] bpf/verifier: improve XOR and OR " Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 4/6] selftests/bpf: XOR and OR range computation tests Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 5/6] bpf/verifier: relax MUL range computation check Cupertino Miranda
2024-05-06 14:18 ` [PATCH bpf-next v5 6/6] selftests/bpf: MUL range computation tests Cupertino Miranda
2024-05-07  0: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=171504122871.27463.1368138144281847004.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=cupertino.miranda@oracle.com \
    --cc=david.faust@oracle.com \
    --cc=eddyz87@gmail.com \
    --cc=elena.zannoni@oracle.com \
    --cc=jose.marchesi@oracle.com \
    --cc=yonghong.song@linux.dev \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).