From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, a.s.protopopov@gmail.com,
dwindsor@gmail.com
Subject: Re: [PATCH bpf-next] resolve_btfids: Don't list -EBUSY next to -EINPROGRESS
Date: Sun, 15 Nov 2026 02:00:05 +0000 [thread overview]
Message-ID: <179470800504.2445485.14147273883421189279.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261114232754.2732901-1-alexei.starovoitov@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 14 Nov 2026 23:27:54 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> crypto_enqueue_request() returns three codes. Only -ENOSPC is a failure:
>
> int err = -EINPROGRESS;
>
> if (unlikely(queue->qlen >= queue->max_qlen)) {
> if (!(request->flags & CRYPTO_TFM_REQ_MAY_BACKLOG)) {
> err = -ENOSPC;
> goto out;
> }
> err = -EBUSY;
> ..
> }
> queue->qlen++;
> list_add_tail(&request->list, &queue->list);
> out:
> return err;
>
> [...]
Here is the summary with links:
- [bpf-next] resolve_btfids: Don't list -EBUSY next to -EINPROGRESS
https://git.kernel.org/bpf/bpf-next/c/8835113107b2
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:[~2026-11-15 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 23:27 [PATCH bpf-next] resolve_btfids: Don't list -EBUSY next to -EINPROGRESS Alexei Starovoitov
2026-11-15 0:07 ` bot+bpf-ci
2026-11-15 2:00 ` 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=179470800504.2445485.14147273883421189279.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dwindsor@gmail.com \
--cc=eddyz87@gmail.com \
--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.