Messages in this thread | | | Date | Thu, 11 Jul 2002 13:07:38 -0500 | From | Anton Blanchard <> | Subject | Re: [STATUS 2.5] July 10, 2002 |
| |
> You need a bit more than that. You need a consistent way to report > an IRQ number, a device name, a PCI object etc. That does mean tidying up > printk but not in a bad way. One can imagine either > > "%s", irq_name(irq) > > or > "%I", irq > > type solutions
This would be nice. Ive been meaning to clean up the sparc64 irq printing macros so I can use them on ppc64 (we have sparse irqs and map them dynamically into the irq_desc array).
Same problem once we get PCI domains. So this cleanup will help more than just event logging.
Anton - 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/
| |