Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 11 Jul 2002 19:25:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 11 Jul 2002 19:25:47 -0400 Received: from samba.sourceforge.net ([198.186.203.85]:52192 "HELO lists.samba.org") by vger.kernel.org with SMTP id ; Thu, 11 Jul 2002 19:25:46 -0400 Date: Thu, 11 Jul 2002 13:07:38 -0500 From: Anton Blanchard To: Alan Cox Cc: Larry Kessler , Kurt Garloff , Perches Joe , thunder@ngforever.de, bunk@fs.tum.de, boissiere@adiglobal.com, linux-kernel@vger.kernel.org, "'Martin.Bligh@us.ibm.com'" , Rusty Russell Subject: Re: [STATUS 2.5] July 10, 2002 Message-ID: <20020711180738.GB6002@krispykreme> References: <3D2C88B2.FF9ECD5C@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 795 Lines: 25 > 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/