summaryrefslogtreecommitdiff
path: root/include/uapi/linux
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2026-07-03 08:57:18 +0200
committerPaolo Abeni <pabeni@redhat.com>2026-07-03 08:57:18 +0200
commit6fb33632323a396c9dc2bb9bea483e013e547d57 (patch)
tree5a8c610384d74ba4b391ec028224add1dc4f30f5 /include/uapi/linux
parent8d96107b5828be42c7ece7bba0e590811052e9dd (diff)
parent10c90f1bba3ad979b77f0778e295fb974e78f0cc (diff)
Merge branch 'tools-ynl-pyynl-pull-the-family-resolution-logic-into-the-lib'
Jakub Kicinski says: ==================== tools: ynl: pyynl: pull the --family resolution logic into the lib When packaging YNL as a system level utility we added a --family argument which auto-resolves the full spec path from a well known path in /usr/share. Spelling out full YAML spec files is at this point only done in-tree, for example in the selftests which need the very latest YAML. But the selftests have their own wrapping classes for each family so test authors aren't really bothered by having to spell the paths out. Afford the same ease of use to the Python library users. Move the path resolution from the CLI code to the library. This simplifies the pyynl use by a lot: from pyynl import YnlFamily ynl = YnlFamily(family="netdev") Unless I'm missing a trick, resolving the /usr/share path is hard enough for most users to lean towards shelling out to ynl CLI with --output-json, which is sad. v1: https://lore.kernel.org/20260630001432.2204298-3-kuba@kernel.org ==================== Link: https://patch.msgid.link/20260701021751.3234681-1-kuba@kernel.org Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions