From: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
To: Armin <akuster@pacbell.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] Several patches against linuxppc_devel-2.4.18-rc1
Date: Mon, 18 Feb 2002 13:35:05 +0100 [thread overview]
Message-ID: <3C70F4F9.7010503@elsoft.ch> (raw)
In-Reply-To: 3C6FCBFD.80504@pacbell.net
Hi
Armin wrote:
> David Müller (ELSOFT AG) wrote:
>
>> Hello
>>
>> - arch/ppc/kernel/ppc4xx_pic.c
>> fixed constant in ppc405_pic_get_irq()
>> (NR_IRQS is not necessarily the total number of UIC irqs)a
>
>
> hmmmmm... we should get ride of "NR_BOARD_IRQS" instead?
>
What do you mean by "get ride of "NR_BOARD_IRQS"".
Remove "NR_BOARD_IRQS" and the whole functionality behind of it
completely or just replace "NR_BOARD_IRQS" by a more meaningful name?
Dave
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-02-18 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 12:52 [PATCH] Several patches against linuxppc_devel-2.4.18-rc1 David Müller (ELSOFT AG)
2002-02-17 15:27 ` Armin
2002-02-18 12:35 ` David Müller (ELSOFT AG) [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=3C70F4F9.7010503@elsoft.ch \
--to=d.mueller@elsoft.ch \
--cc=akuster@pacbell.net \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).