Jason Nymble <jason.nymble@xxxxxxxxx> writes: > Also, unless I'm mistaken, you can't/shouldn't call printk from > interrupt context? Ooh. That would be inconvenient. For examples of printk being called from interrupt context, look for error handling around allocations with GFP_ATOMIC. The comment above the definition of the printk function starts with, /** * printk - print a kernel message * @fmt: format string * * This is printk(). It can be called from any context. We want it to work. -- Ed Cashin <ecashin@xxxxxxxxxx> Find experimental aoe Linux driver patches at http://coraid.typepad.com/aoe_linux_proving_grounds/ -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
