From: Anton Blanchard <anton@samba.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Larry Kessler <kessler@us.ibm.com>,
Kurt Garloff <garloff@suse.de>,
Perches Joe <joe.perches@spirentcom.com>,
thunder@ngforever.de, bunk@fs.tum.de, boissiere@adiglobal.com,
linux-kernel@vger.kernel.org,
"'Martin.Bligh@us.ibm.com'" <Martin.Bligh@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [STATUS 2.5] July 10, 2002
Date: Thu, 11 Jul 2002 13:07:38 -0500 [thread overview]
Message-ID: <20020711180738.GB6002@krispykreme> (raw)
In-Reply-To: <E17SOoL-0007q9-00@the-village.bc.nu>
> 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
next prev parent reply other threads:[~2002-07-11 23:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 17:46 Perches, Joe
2002-07-10 18:05 ` Thunder from the hill
2002-07-10 18:38 ` Alan Cox
2002-07-10 18:49 ` Kurt Garloff
2002-07-10 19:19 ` Larry Kessler
2002-07-10 21:15 ` Alan Cox
2002-07-11 18:07 ` Anton Blanchard [this message]
2002-07-10 21:27 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 20:34 Richard J Moore
2002-07-13 9:28 ` Ingo Oeser
2002-07-11 19:21 Richard J Moore
2002-07-10 18:08 Russ Weight
2002-07-10 5:11 Guillaume Boissiere
2002-07-10 15:49 ` Rik van Riel
2002-07-10 16:19 ` Adrian Bunk
2002-07-10 16:31 ` Thunder from the hill
2002-07-10 16:51 ` Roman Zippel
2002-07-10 17:00 ` Thunder from the hill
2002-07-10 16:54 ` Karim Yaghmour
2002-07-10 17:25 ` John Levon
2002-07-10 19:19 ` Karim Yaghmour
2002-07-10 17:17 ` Alan Cox
2002-07-10 20:21 ` Daniel Phillips
2002-07-10 17:12 ` Patrick Mochel
2002-07-10 17:42 ` Arnaldo Carvalho de Melo
2002-07-10 17:54 ` Robert Love
2002-07-10 19:18 ` Ville Herva
2002-07-10 20:03 ` Robert Love
2002-07-10 20:20 ` Cort Dougan
2002-07-10 20:25 ` Robert Love
2002-07-10 20:41 ` Ville Herva
2002-07-10 21:07 ` Alan Cox
2002-07-10 20:46 ` Robert Love
2002-07-11 9:46 ` Rogier Wolff
2002-07-10 20:26 ` Justin M. Forbes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020711180738.GB6002@krispykreme \
--to=anton@samba.org \
--cc=Martin.Bligh@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=boissiere@adiglobal.com \
--cc=bunk@fs.tum.de \
--cc=garloff@suse.de \
--cc=joe.perches@spirentcom.com \
--cc=kessler@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=thunder@ngforever.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®