From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Amrani, Ram" Subject: RE: [RFC 00/11] QLogic RDMA Driver (qedr) RFC Date: Wed, 14 Sep 2016 14:44:47 +0000 Message-ID: References: <1473696465-27986-1-git-send-email-Ram.Amrani@qlogic.com> <20160912180508.GI5843@obsidianresearch.com> <20160913154000.GA25878@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20160913154000.GA25878-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> Content-Language: en-US Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jason Gunthorpe Cc: "dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , David Miller , Yuval Mintz , Ariel Elior , Michal Kalderon , Rajesh Borundia , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , netdev List-Id: linux-rdma@vger.kernel.org > Anything that is used with copy_to/from_user, ib_copy_to/from_udata,=20 > etc, etc must be in a include/uapi header. >=20 > Any constant you might want to copy into your userspace provider must=20 > be in include/uapi. >=20 I understand you mean something like https://www.spinics.net/lists/linux-rd= ma/msg40414.html ([RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI dir= ectory) > Avoid copying headers in your user space and use the standard kernel=20 > names to access your driver's uapi. So the user library should be able to compile against these headers in thei= r 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html