All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, mhartmay@linux.ibm.com, iii@linux.ibm.com
Subject: Re: [PATCH bpf-next v2 0/3] bpf: Some fixes for nullness elision
Date: Fri, 07 Feb 2025 23:50:35 +0000	[thread overview]
Message-ID: <173897223576.2425305.593273942477450759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1738689872.git.dxu@dxuuu.xyz>

Hello:

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

On Tue,  4 Feb 2025 10:25:15 -0700 you wrote:
> Two fixes for nullness elision. See commits for more details.
> 
> === Changelog ===
> Changes from v1:
> * Reword commit message in patch 1
> * Add tags
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/3] bpf: verifier: Do not extract constant map keys for irrelevant maps
    https://git.kernel.org/bpf/bpf/c/884c3a18dadf
  - [bpf-next,v2,2/3] bpf: selftests: Test constant key extraction on irrelevant maps
    https://git.kernel.org/bpf/bpf/c/973cb1382ead
  - [bpf-next,v2,3/3] bpf: verifier: Disambiguate get_constant_map_key() errors
    https://git.kernel.org/bpf/bpf/c/7968c6581507

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



      parent reply	other threads:[~2025-02-07 23:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 17:25 [PATCH bpf-next v2 0/3] bpf: Some fixes for nullness elision Daniel Xu
2025-02-04 17:25 ` [PATCH bpf-next v2 1/3] bpf: verifier: Do not extract constant map keys for irrelevant maps Daniel Xu
2025-02-04 17:25 ` [PATCH bpf-next v2 2/3] bpf: selftests: Test constant key extraction on " Daniel Xu
2025-02-04 17:25 ` [PATCH bpf-next v2 3/3] bpf: verifier: Disambiguate get_constant_map_key() errors Daniel Xu
2025-02-07 23:50 ` 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=173897223576.2425305.593273942477450759.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dxu@dxuuu.xyz \
    --cc=iii@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mhartmay@linux.ibm.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.