On Mon, May 08, 2017 at 10:30:29PM +0530, Devesh Sharma wrote: > > Relying on the kernel header from a uapi header means that we now > > require the distro to have a sufficient version of that kernel header. > Which means we need to have a mechanism to track the versions. > is relying on the ABI version is good enough or you see any blockers > there.. Realistically I think it means those distros will have to be de-supported. This might not be a problem, the uapi headers are fairly old now, you'll have to check.. If something really old like rhel6 has what you need then things are OK. > > This might be OK, but you have to check to see what distros are > > including (cbuild --run-shell can help with this) > And if a given distro is not including then fall-back to current > scheme, is it okay to have defining/un-defining compile time macros > to enable/disable certain code sections? No, generally not. This is too hard to do safely in public headers.. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
