From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nicolas DET <nd@bplan-gmbh.de>
Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org, sl@bplan-gmbh.de,
sha@pengutronix.de, linuxppc-embedded@ozlabs.org
Subject: Re: Re: [PATCH] General CHRP/MPC5K2 platform support patch
Date: Sun, 29 Oct 2006 07:12:24 +1100 [thread overview]
Message-ID: <1162066344.25682.126.camel@localhost.localdomain> (raw)
In-Reply-To: <200610281343.k9SDhTJm020310@post.webmailer.de>
> > As I said before, NR_IRQ is a poor choice for the size of the revmap.
> > You should have a constant somewhere defining what is your max HW irq
> > number. and use that +1, or a hw irq count.
>
> Done: 64
Even with a new numbering invloving the category in top bits and the bit
number in the bottom ?
Ben.
prev parent reply other threads:[~2006-10-28 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 13:43 Re: [PATCH] General CHRP/MPC5K2 platform support patch Nicolas DET
2006-10-28 20:12 ` Benjamin Herrenschmidt [this message]
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=1162066344.25682.126.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=nd@bplan-gmbh.de \
--cc=sha@pengutronix.de \
--cc=sl@bplan-gmbh.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;
as well as URLs for NNTP newsgroup(s).