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, jiri@resnulli.us
Subject: Re: [PATCH net] tools: ynl-gen: always construct struct ynl_req_state
Date: Wed, 29 Nov 2023 16:50:27 +0000 [thread overview]
Message-ID: <170127662761.14566.593097773218186223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231126225858.2144136-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 26 Nov 2023 14:58:58 -0800 you wrote:
> struct ynl_req_state carries reply-related info from generated code
> into generic YNL code. While we don't need reply info to execute
> a request without a reply, we still need to pass in the struct, because
> it's also where we get the pointer to struct ynl_sock from. Passing NULL
> results in crashes if kernel returns an error or an unexpected reply.
>
> Fixes: dc0956c98f11 ("tools: ynl-gen: move the response reading logic into YNL")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net] tools: ynl-gen: always construct struct ynl_req_state
https://git.kernel.org/netdev/net/c/83f2df9d66bc
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-11-29 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 22:58 [PATCH net] tools: ynl-gen: always construct struct ynl_req_state Jakub Kicinski
2023-11-29 16:50 ` 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=170127662761.14566.593097773218186223.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).