summaryrefslogtreecommitdiff
path: root/scripts/lib/kdoc/kdoc_files.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-06-25 15:36:30 -0700
committerJakub Kicinski <kuba@kernel.org>2025-06-25 15:36:31 -0700
commit9186c43c1f000ce18069b429afcc725c2997d040 (patch)
treeaa51d72493612b27fefe84ecdc11cee177596158 /scripts/lib/kdoc/kdoc_files.py
parent7b515f35a911fdc31fbde6531828dcd6ae9803d3 (diff)
parentaf852f1f1c951d43b36881302fd10d9f898cdb54 (diff)
Merge branch 'netlink-specs-enforce-strict-naming-of-properties'
Jakub Kicinski says: ==================== netlink: specs: enforce strict naming of properties I got annoyed once again by the name properties in the ethtool spec which use underscore instead of dash. I previously assumed that there is a lot of such properties in the specs so fixing them now would be near impossible. On a closer look, however, I only found 22 (rough grep suggests we have ~4.8k names in the specs, so bad ones are just 0.46%). Add a regex to the JSON schema to enforce the naming, fix the few bad names. I was hoping we could start enforcing this from newer families, but there's no correlation between the protocol and the number of errors. If anything classic netlink has more recently added specs so it has fewer errors. The regex is just for name properties which will end up visible to the user (in Python or YNL CLI). I left the c-name properties alone, those don't matter as much. C codegen rewrites them, anyway. I'm not updating the spec for genetlink-c. Looks like it has no users, new families use genetlink, all old ones need genetlink-legacy. If these patches are merged I will remove genetlink-c completely in net-next. ==================== Link: https://patch.msgid.link/20250624211002.3475021-1-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions