Messages in this thread |  | | Subject | Re: __bad_udelay in 2.2.18pre15 | Date | Wed, 11 Oct 2000 17:27:26 +0100 (BST) | From | Alan Cox <> |
| |
> >> #define udelay(n) (__builtin_constant_p(n) ? \ > >> ((n) > 20000 ? __bad_udelay() : __const_udelay((n) * > >> 0x10c6ul)) : \ > >> __udelay(n)) > >> > >> ... > >> It seems __bad_udelay is not defined anywhere in the kernel source. > > > >Correct. Its a compile time error trap > > Well, at first, I wanted to implement it the same way on PPC. However, it > dies on all occurences where udelay is called with a non-constant expression.
__builtin_constant_p means non constant expressions will always call udelay
> I spotted this case in a few PPC specific stuffs (fixable), but also in > the sys_nanosleep code, and in the de4x5 driver.
I'll check these two
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |