From: Jeff Baitis <baitisj@evolution.com>
To: Pete Popov <ppopov@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: arch/mips/au1000/common/irq.c
Date: Thu, 13 Mar 2003 10:47:04 -0800 [thread overview]
Message-ID: <20030313104704.V20129@luca.pas.lab> (raw)
Pete:
I've got a question concerning irq.c. In intc0_req0_irqdispatch() (linux_2_4
branch) on lines 545 thru 552, the code reads:
for (i=0; i<32; i++) {
if ((intc0_req0 & (1<<i))) {
intc0_req0 &= ~(1<<i);
do_IRQ(irq, regs);
break;
}
irq++;
}
My question is: why do we increment i and irq independently?
Why doesn't the code read:
for (i=0; i<32; i++) {
if ((intc0_req0 & (1<<i))) {
intc0_req0 &= ~(1<<i);
do_IRQ(i, regs);
break;
}
}
Thanks for your help!
-Jeff
--
Jeffrey Baitis - Associate Software Engineer
Evolution Robotics, Inc.
130 West Union Street
Pasadena CA 91103
tel: 626.535.2776 | fax: 626.535.2777 | baitisj@evolution.com
next reply other threads:[~2003-03-13 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 18:47 Jeff Baitis [this message]
2003-03-13 18:50 ` arch/mips/au1000/common/irq.c Dan Malek
2003-03-13 22:13 ` arch/mips/au1000/common/irq.c Jeff Baitis
2003-03-13 22:25 ` arch/mips/au1000/common/irq.c Jeff Baitis
2003-03-13 18:59 ` arch/mips/au1000/common/irq.c Pete Popov
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=20030313104704.V20129@luca.pas.lab \
--to=baitisj@evolution.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
/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