Re: [PATCH] new system call mknod64

Andries.Brouwer
2003-04-20T21:14:27Z

From davem@redhat.com Sun Apr 20 23:12:17 2003

> Yesterday or the day before Linus preferred __u32 etc for this
> loopinfo64 ioctl, so I did it that way. Here, since mknod is a
> traditional Unix system call, I am still inclined to prefer
> (unsigned) int above __u32. Of course it doesn't matter much.

To 64-bit platforms implementing 32-bit compatability layers,
it can matter a ton to use portable vs. non-portable types.

Such an abstract statement nobody can disagree with.
Do you have an opinion in the mknod case?

(For example, I do not suppose anybody would argue that
open() should return an __u32 instead of an int.)

Andries