From: Ian Campbell <ijc@hellion.org.uk>
To: Miles Bader <miles@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: irq 0?
Date: Mon, 07 Nov 2005 12:25:52 +0000 [thread overview]
Message-ID: <1131366352.14696.60.camel@icampbell-debian> (raw)
In-Reply-To: <buobr0wbrme.fsf@dhapc248.dev.necel.com>
On Mon, 2005-11-07 at 20:54 +0900, Miles Bader wrote:
> I notice that arch/v850/kernel/irq.c has been updated with a
> "show_interrupts" function; in this function it contains the following
> bit of code:
>
>
> if (i == 0) {
> seq_puts(p, " ");
> for (i=0; i < 1 /*smp_num_cpus*/; i++)
> seq_printf(p, "CPU%d ", i);
> seq_putc(p, '\n');
> }
>
> if (i < NR_IRQS) {
> ... show interrupt i ...
> } else if (i == NR_IRQS)
> seq_printf(p, "ERR: %10lu\n", irq_err_count);
>
> where "i" is iterated (by procfs) from 0...NR_IRQS.
>
> On the v850, irq 0 is a real interrupt, so this doesn't really work
> properly -- it doesn't display an entry for irq 0.
What makes you say that? The i==0 code seems to fall through and
therefore should print IRQ0 just fine.
Ian.
--
Ian Campbell
Current Noise: Vader - The Final Massacre
Ignore previous fortune.
next prev parent reply other threads:[~2005-11-07 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 11:54 irq 0? Miles Bader
2005-11-07 12:25 ` Ian Campbell [this message]
2005-11-07 12:57 ` Miles Bader
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=1131366352.14696.60.camel@icampbell-debian \
--to=ijc@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
/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