On Tue, Apr 16, 2013 at 5:59 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > On Tue, Apr 16, 2013 at 7:21 AM, Miklos Szeredi <mik...@szeredi.hu> wrote: >> >> And I still disagree. Why should userspace use the linux internal >> header when there's a perfectly good standard header that it can use? > > If it's called UAPI, it damn well is *meant* for user-space inclusion. > Look at the file-name. > > And since the bug comment says "This file defines the kernel interface > of FUSE" *AND* it very clearly has explicit code to support user-space > includes with special user-space-only type defines, then your email is > obviously just pure crap, and I don't understand how you can write > that sentence with a straight face.
I think I meant something different by that sentence than what you think I meant :) What I meant is IF <linux/fuse.h> is included by userspace (it sure is meant to be included and *is* included by libfuse and other stuff) THEN using <stdint.h> instead of <linux/types.h> is fine regardless of whether __linux__ is defined or not. Does that sound better, or is there still something we disagree about? Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
