Jakub Kicinski 83f2df9d66 tools: ynl-gen: always construct struct ynl_req_state ... 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: dc0956c98f ("tools: ynl-gen: move the response reading logic into YNL") Link: https://lore.kernel.org/r/20231126225858.2144136-1-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>		2023-11-29 08:44:02 -08:00
..
generated	tools: ynl-gen: always construct struct ynl_req_state	2023-11-29 08:44:02 -08:00
lib	tools: ynl: introduce option to process unknown attributes or types	2023-10-27 14:54:31 -07:00
samples	tools: ynl: use uAPI include magic for samples	2023-10-04 17:33:54 -07:00
cli.py	tools: ynl: introduce option to process unknown attributes or types	2023-10-27 14:54:31 -07:00
ethtool.py	tools: ynl: Rename ethtool to ethtool.py	2023-04-13 22:18:29 -07:00
Makefile	tools: ynl: don't regen on every make	2023-10-04 17:33:54 -07:00
Makefile.deps	tools: ynl: fix header path for nfsd	2023-11-23 08:52:12 -08:00
requirements.txt	tools: ynl: add the Python requirements.txt file	2023-03-24 19:11:02 -07:00
ynl-gen-c.py	tools: ynl-gen: always construct struct ynl_req_state	2023-11-29 08:44:02 -08:00
ynl-regen.sh	ynl: regenerate all headers	2023-07-28 09:33:12 -07:00