All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jules Irenge <jbi.octave@gmail.com>
Cc: ast@kernel.org, memxor@gmail.com, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	Elana.Copperman@mobileye.com
Subject: Re: [PATCH bpf-next] Fixes: 14a324f6a67e ("bpf: Wire up freeing of referenced kptr")
Date: Wed, 07 Sep 2022 18:20:15 +0000	[thread overview]
Message-ID: <166257481530.10994.18003275346463171188.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YxR9v/dyzDt8sBFT@playground>

Hello:

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

On Sun, 4 Sep 2022 11:28:15 +0100 you wrote:
> This patch fixes a warning generated by Sparse
> 
> "warning: Using plain integer as NULL pointer"
> 
> by replacing p with *p in the WRITE_ONCE() macro
> 
> This enables the pointer to be cleared on map value delete,
> hence clearing the warning.
> 
> [...]

Here is the summary with links:
  - [bpf-next] Fixes: 14a324f6a67e ("bpf: Wire up freeing of referenced kptr")
    https://git.kernel.org/bpf/bpf-next/c/9fad7fe5b298

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-09-07 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 10:28 [PATCH bpf-next] Fixes: 14a324f6a67e ("bpf: Wire up freeing of referenced kptr") Jules Irenge
2022-09-04 21:10 ` Kumar Kartikeya Dwivedi
2022-09-07 18:20 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-04 10:18 Jules Irenge

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=166257481530.10994.18003275346463171188.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Elana.Copperman@mobileye.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jbi.octave@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --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 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.