Re: __bad_udelay in 2.2.18pre15

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Wed Oct 11 2000 - 17:58:12 EDT

Next message: Linus Torvalds: "Re: test10-pre1 problems on 4-way SuperServer8050"

Previous message: Miles Lane: "Second attempt -- Re: 2.4.0-test10-pre1 + APIC,NMI Watchdog (latest) -- OOPS -- Unable to handle null pointer dereference"
In reply to: Chris Swiedler: "RE: __bad_udelay in 2.2.18pre15"
Next in thread: Horst von Brand: "Re: __bad_udelay in 2.2.18pre15"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Wouldn't it be better to use an #error directive? I'm sure this could turn
> into a FAQ, even though the symbol is called "__bad_udelay()".

You cant do that trick since #error is pre-processor, otherwise - yes

>

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

Next message: Linus Torvalds: "Re: test10-pre1 problems on 4-way SuperServer8050"
Previous message: Miles Lane: "Second attempt -- Re: 2.4.0-test10-pre1 + APIC,NMI Watchdog (latest) -- OOPS -- Unable to handle null pointer dereference"
In reply to: Chris Swiedler: "RE: __bad_udelay in 2.2.18pre15"
Next in thread: Horst von Brand: "Re: __bad_udelay in 2.2.18pre15"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Oct 11 2000 - 17:59:54 EDT