On Tue, 5 May 2026 17:06:25 -0700 Jakub Kicinski wrote: > + description: | > + Visibility of this definition. "uapi" (default) renders into > + the uAPI header, "kernel" renders into the kernel-side > + generated header, "user" renders into the user-side > + generated header. When combined with `header:`, the > + definition is not rendered, and the named header is > + included only by code matching the scope.
Clashiko says I'm not implementing enum handling even tho the param is generic. True, but intentional. Since this is primarily for policies I don't think we'll need an enum. We tend not to implement things we don't use in the code gen. I implemented header handling here (even tho it's not used) because I think that part is tricky (read: I would have forgotten the plan/thinking if I didn't just implement it right away).
