> You know, this use case seems unavoidable so I'll just proceed with the > configurability of it. But note that it seems we're both in agreement > that right now what you described requires more work before in any way > shape or form folks start using it for the exact purpose you described. > I also think Andi Kleen's module namespace might be a much better solution to > that problem [0], we'd just have to carry the code ourselves as I am not Just to clarify. My name spaces didn't really provide different name spaces (like C++), it just added a ACL to exports to make it possible to do "export only to module N". But the name space itself was still flat On the linker side doing real name spaces is probably not too hard, but it would be difficult for linked in code without special linker support. > sure if this is ever going to get upstream as it was originally nacked. May need to revisit that. -Andi -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
