[RFC 0/3] Add support for meta keys, bridge family specific

[Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>]

Hi Patrick and Pablo,

I need your input on that one, thus I am sending it as an RFC.

Patch 1 and 2 are straight forward so I'll skip. (though there might be 
improvement to be done. For instance, the init code part is 90% same so
it could be factorized maybe)

Now patch 3: without it, the bridge specific module for meta expression
cannot work: bare meta expression module gets in use since it's generic from
family level.
It's again quite trivial, but I would like your opinion about it.

I was thinking also on different solutions like registering a meta expr type
for every family... but it's not really memory wise.

With patch 3, at worst it loops through the entire expression type list
and this case happens for most of expressions, since they are family agnostic.
So it's not great either...

What do you think?

(Btw, I already made the patches for libnftnl and nftables but I skipped those
for this RFC.)

Tomasz

-- 
1.8.3.2