> Anything that is used with copy_to/from_user, ib_copy_to/from_udata, > etc, etc must be in a include/uapi header. > > Any constant you might want to copy into your userspace provider must > be in include/uapi. > I understand you mean something like https://www.spinics.net/lists/linux-rdma/msg40414.html ([RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI directory) > Avoid copying headers in your user space and use the standard kernel > names to access your driver's uapi. So the user library should be able to compile against these headers in their location and not hold identical copies. What do you mean by "standard kernel names"? Thanks, Ram -- 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
