Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Fri Dec 07 2001 - 17:08:51 EST

Next message: Rik van Riel: "Re: Kernel 2.4.16 & Heavy I/O"
Previous message: Erik Andersen: "Re: On re-working the major/minor system"
In reply to: David Mosberger: "Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)"
Next in thread: Marcelo Tosatti: "Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> >>>>> On Fri, 7 Dec 2001 16:52:07 -0200 (BRST), Marcelo Tosatti <marcelo@conectiva.com.br> said:
> Marcelo> I'm really not willing to apply this kludge...
>
> Do you agree that it should always be safe to call printk() from C code?

Sounds a good goal, but surely thats up to the arch code to get right
-
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/

Next message: Rik van Riel: "Re: Kernel 2.4.16 & Heavy I/O"
Previous message: Erik Andersen: "Re: On re-working the major/minor system"
In reply to: David Mosberger: "Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)"
Next in thread: Marcelo Tosatti: "Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Dec 07 2001 - 21:00:40 EST