From: Vojtech P. <vo...@su...> - 2002-07-30 21:36:02
|
On Tue, Jul 30, 2002 at 02:20:36PM -0700, Linus Torvalds wrote: > On Tue, 30 Jul 2002, Greg KH wrote: >=20 > > On Tue, Jul 30, 2002 at 03:23:42PM +0200, Vojtech Pavlik wrote: > > > -#include <asm/types.h> > > > +#include <stdint.h> > >=20 > > Why? I thought we were not including any glibc (or any other libc) > > header files when building the kernel? >=20 > Indeed. This is unacceptable. >=20 > Especially as the standard types are total crap, and the u8 etc are a l= ot=20 > more readable. People should realize: >=20 > - the "int" is superfluous. Of _course_ it's an integer. If it was a=20 > floating point number, it would be fp16/fp32/fp64/fp80/whatever. > - the "_t" is there only for namespace collisions, sane people can cho= se=20 > to ignore it. >=20 > What do you have left after you have removed the crap? Yup. u8, u16, et= c.=20 > And if you want to share with user space, there's=A0the long-accepted=20 > namespace collision avoidance of prepending two underscores. >=20 > Fix it, Vojtech. >=20 > Linus I will, and will do so happily. I don't like the uint*_t types as well. This change was pushed very heavily for by Brad Hards, based on a conclusion of a rather lengthy discussion (I think on linux-usb) on which types should be used. Now the question remaining is how to fix that? You can just skip the patch. I've tried a 'bk undo', but that complains about unmerged leaves in that case (though really nothing depends on those changes). Or should I just make another cset on top of all the previous? --=20 Vojtech Pavlik SuSE Labs |