On Wed, 2015-09-16 at 13:23 +0200, John Crispin wrote: > thinking about this, the new elements should also be guarded by a #ifdef > CONFIG_lantiq will add that now
You can't do that in user-visible headers. CONFIG_LANTIQ isn't defined in t he userspace builds, so userspace will get a version *without* the additions, and its ABI will be different to that of the kernel. And even if it *did* work that way, you'd still end up needing a *different* build of userspace tools like pppd, depending on the platform it's going to be run on. If you really need these new fields to be visible to userspace, then I think the best option is to add a *new* SO_ATMQOS2 sockopt, and leave the original SO_ATMQOS entirely alone. -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
