[lkml]   [2004]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC] ASLA design, depth of code review and lack thereof
Ladies and gentlemen, may I politely ask what description would fit somebody
who have made the following

union {
float f;
u_int32_t i;
} u;
u.f = 0.0;
return bswap_32(u.i);
return u.i;
and quite a few similar, er, wonders an ioctl?

That's right. This code just has to be in the kernel. It can't be in
a library, oh no. It can't be a trivial macro that would result in
compiler generating the constant, no sir - it just had to be proudly
dumped into the great barfbag in the tree.

And that leads to a really interesting question: how many people had ever
read that code? Or documentation covering that ioctl, while we are at it.

Unless I'm mistaken, ALSA used revision control for a long, long time.
Jaroslav, could you please find the origin of that little wonder and
share with the class - who had done that, why it had been committed into
ALSA tree and how did it manage to survive until the merge into the main
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [W:0.060 / U:3.020 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site