On 8/24/20 1:54 AM, Johannes Berg wrote:
> Arguably, pretty much all of the code here should go into libnetlink
> then, since the kernel facility was expressly written in a way that
> would allow dumping out arbitrary (not just generic netlink) policies,
> just needs wiring up in the appropriate netlink family (or perhaps some
> additional "policy netlink" family?)

good point.

> 
> I can make that change, but I sort of assumed it'd be nicer to do that
> when someone else actually picked it up.

I think it would be better to put this into libnetlink from the start.

Reply via email to