From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, jdamato@fastly.com, almasrymina@google.com,
sridhar.samudrala@intel.com, amritha.nambiar@intel.com
Subject: Re: [PATCH net v2 1/2] netdev-genl: avoid empty messages in napi get
Date: Fri, 20 Dec 2024 21:00:31 +0000 [thread overview]
Message-ID: <173472843153.3019277.8963909942881596835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241219032833.1165433-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 Dec 2024 19:28:32 -0800 you wrote:
> Empty netlink responses from do() are not correct (as opposed to
> dump() where not dumping anything is perfectly fine).
> We should return an error if the target object does not exist,
> in this case if the netdev is down we "hide" the NAPI instances.
>
> Fixes: 27f91aaf49b3 ("netdev-genl: Add netlink framework functions for napi")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net,v2,1/2] netdev-genl: avoid empty messages in napi get
https://git.kernel.org/netdev/net/c/4a25201aa46c
- [net,v2,2/2] selftests: drv-net: test empty queue and NAPI responses in netlink
https://git.kernel.org/netdev/net/c/30b981796b94
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:[~2024-12-20 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 3:28 [PATCH net v2 1/2] netdev-genl: avoid empty messages in napi get Jakub Kicinski
2024-12-19 3:28 ` [PATCH net v2 2/2] selftests: drv-net: test empty queue and NAPI responses in netlink Jakub Kicinski
2024-12-19 13:28 ` [PATCH net v2 1/2] netdev-genl: avoid empty messages in napi get Eric Dumazet
2024-12-20 21: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=173472843153.3019277.8963909942881596835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.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.