From: patchwork-bot+netdevbpf@kernel.org
To: Tobias Klauser <tklauser@distanz.ch>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev
Subject: Re: [PATCH bpf-next] bpf: Drop always true do_idr_lock parameter to bpf_map_free_id
Date: Fri, 03 Feb 2023 04:40:17 +0000 [thread overview]
Message-ID: <167539921711.12589.8835634003496821011.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230202141921.4424-1-tklauser@distanz.ch>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 2 Feb 2023 15:19:21 +0100 you wrote:
> The do_idr_lock parameter to bpf_map_free_id was introduced by commit
> bd5f5f4ecb78 ("bpf: Add BPF_MAP_GET_FD_BY_ID"). However, all callers set
> do_idr_lock = true since commit 1e0bd5a091e5 ("bpf: Switch bpf_map ref
> counter to atomic64_t so bpf_map_inc() never fails").
>
> While at it also inline __bpf_map_put into its only caller bpf_map_put
> now that do_idr_lock can be dropped from its signature.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Drop always true do_idr_lock parameter to bpf_map_free_id
https://git.kernel.org/bpf/bpf-next/c/158e5e9eeaa0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-03 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 14:19 [PATCH bpf-next] bpf: Drop always true do_idr_lock parameter to bpf_map_free_id Tobias Klauser
2023-02-03 4:40 ` 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=167539921711.12589.8835634003496821011.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=martin.lau@linux.dev \
--cc=tklauser@distanz.ch \
/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