From: patchwork-bot+netdevbpf@kernel.org
To: Igor Opaniuk <igor.opaniuk@oss.qualcomm.com>
Cc: mani@kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, christopher.lew@oss.qualcomm.com
Subject: Re: [PATCH net v2] net: qrtr: ns: keep notifying local servers after a failed send
Date: Sat, 21 Nov 2026 02:00:22 +0000 [thread overview]
Message-ID: <179522642228.886068.11407811998748570053.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261114-upstream-qrtr-hello-gate-fix_b4-v2-1-2fb62c2853bb@oss.qualcomm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 14 Nov 2026 13:46:11 +0100 you wrote:
> ctrl_cmd_bye() and ctrl_cmd_del_client() forward the event to every
> local server, but stop at the first failed send. Each send goes to a
> different socket, so a single server with a full receive queue
> (-ENOSPC) hides the event from all servers after it.
>
> Log the failure and carry on. Likewise, keep notifying local lookups
> when the NEW_SERVER broadcast fails, which can only happen on -ENOMEM.
>
> [...]
Here is the summary with links:
- [net,v2] net: qrtr: ns: keep notifying local servers after a failed send
https://git.kernel.org/netdev/net/c/925120216e6d
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-21 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 12:46 Igor Opaniuk
2026-11-21 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=179522642228.886068.11407811998748570053.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christopher.lew@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=igor.opaniuk@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®