Messages in this thread | | | Subject | Re: printk() with a spin-lock held. | From | Lee Revell <> | Date | Mon, 25 Oct 2004 14:41:12 -0400 |
| |
On Mon, 2004-10-25 at 08:32 -0400, Richard B. Johnson wrote: > I recall that printk() useds to just write stuff into a buffer, > that the buffer (the same buffer used for dmesg), was written > out only when it was safe to do so. > > > Now, if printk() can't do that anymore, how does one de-bug > ISR code? Or do you just heave it off the cliff and hope that > it flies?
No, it can, I was wrong. I was thinking of some other function.
Lee
- 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/
| |