Re: [PATCH] Beginnings of conpat 32 code cleanups

From: Linus Torvalds (torvalds@transmeta.com)
Date: Fri Nov 22 2002 - 14:47:27 EST


On Fri, 22 Nov 2002, Stephen Rothwell wrote:
>
> This patch merely adds include/asm-generic/compat32.h which is the header
> information that is common to all the 32 bit compatibility code across all
> the architectures (except parisc as I don't pretend to understand that
> :-)).

What kind of strange _crap_ is this?

        +typedef unsigned int __kernel_size_t32;
        +typedef int __kernel_ssize_t32;
        +typedef int __kernel_time_t32;
        +typedef int __kernel_clock_t32;
        +typedef int __kernel_pid_t32;
        +typedef unsigned int __kernel_ino_t32;
        +typedef int __kernel_daddr_t32;
        +typedef int __kernel_off_t32;
        +typedef unsigned int __kernel_caddr_t32;
        +typedef long __kernel_loff_t32;

You're doing a compat layer, and then you're using various undefined types
that can be random sizes, and calling them xxx_t32.

For christ sake, somebody is on drugs here.

If they are called "xxx_t32", then that means that you _know_ the size
already statically, and you should use "u32" or "s32" which are shorter
and clearer anyway. You should sure as hell not use some random C type
that can be different depending on compiler options etc, and then calling
it a "compat" library.

Quite frankly, I don't see the point of this AT ALL. You're introducing
new types that cannot be sanely used directly anyway. What's the point?

Make your compat stuff use u32/s32/u64 directly, instead of making up ugly
new types that make no sense.

                Linus

-
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/



This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:41 EST