On Wed, Sep 14, 2016 at 02:44:47PM +0000, Amrani, Ram wrote: > > 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) Yes. > > 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. Yes, but you will need identical copies for supporting old distros. > What do you mean by "standard kernel names"? By that I mean 'identical copies' do not copy the file and then randomly change it giving things different names or putting different content in structs. You will want to submit your user provider to rdma-plumbing to get it into the distros, we are planning to set it as the vehicle for code targeting 4.9 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
