On Fri, 2015-01-09 at 17:01 +0100, Christoph Hellwig wrote: > On Fri, Jan 09, 2015 at 07:50:38AM -0800, James Bottomley wrote: > > Right, that's why I'm dubious about this effort. uapi files either have > > to become the glibc headers or be exported in a way that allows > > inclusion into glibc headers for there to be any point. > > uapi headers are not just for glibc, they are for any userspace > application. Most of our uapi files aren't used by glibc at all. Yes, but they have to be delivered to users somehow. If you look at debian, they deliver the headers through the linux-dev-libc package which installs into the /usr/include directory. Since glibc currently owns the entirety of /usr/include/scsi, we have to help the distros figure out how we deliver the headers, otherwise all uapi exports of SCSI stuff just gets ignored ... as it does today because there are no kernel SCSI uapi headers in linux-libc-dev. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
