Re: [PATCH] new system call mknod64

Andries.Brouwer@cwi.nl
Mon, 21 Apr 2003 23:48:01 +0200 (MEST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andrew Morton: "Re: 67-mjb2 vs 68-mjb1 (sdet degredation)"
Previous message: Andy Pfiffer: "[KEXEC][2.5.68] kexec for 2.5.68 available"
Maybe in reply to: Andries.Brouwer@cwi.nl: "[PATCH] new system call mknod64"
Next in thread: Linus Torvalds: "Re: [PATCH] new system call mknod64"
Reply: Linus Torvalds: "Re: [PATCH] new system call mknod64"

> Let's go for 32:32 internal and simply map upon mknod(2) and friends.
> On the syscall boundary. End of problem.

Yes. I hope you don't mind that I called this 32:32 monster kdev_t.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Andrew Morton: "Re: 67-mjb2 vs 68-mjb1 (sdet degredation)"
Previous message: Andy Pfiffer: "[KEXEC][2.5.68] kexec for 2.5.68 available"
Maybe in reply to: Andries.Brouwer@cwi.nl: "[PATCH] new system call mknod64"
Next in thread: Linus Torvalds: "Re: [PATCH] new system call mknod64"
Reply: Linus Torvalds: "Re: [PATCH] new system call mknod64"