From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Takayoshi Kochi <t-kochi@bq.jp.nec.com>,
bjorn.helgaas@hp.com, acpi-devel@lists.sourceforge.net,
kaneshige.kenji@soft.fujitsu.com, akpm@osdl.org, greg@kroah.com,
len.brown@intel.com, tony.luck@intel.com,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [ACPI] [PATCH] PCI IRQ resource deallocation support [2/3]
Date: Mon, 27 Sep 2004 14:01:28 +0900 [thread overview]
Message-ID: <41579EA8.8000700@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0409242236330.7426@poirot.grange>
Hi Guennadi Liakhovetski,
Thank you for the information.
I refer to arm, arm26 and ppc64 codes.
Thanks,
Kenji Kaneshige
Guennadi Liakhovetski wrote:
> On Fri, 24 Sep 2004, Kenji Kaneshige wrote:
>
>> Takayoshi Kochi wrote:
>> I'll change my patch to leave dev->irq as it is. And then I'll
>> investigate about defining PCI_UNDEFINED_IRQ.
>
>
> Some platforms (arm, arm26, ppc64) define a macro NO_IRQ:
>
> include/asm-arm/irq.h:#define NO_IRQ ((unsigned int)(-1))
> include/asm-arm26/irq.h:#define NO_IRQ ((unsigned int)(-1))
> include/asm-ppc64/irq.h:#define NO_IRQ (-1)
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
prev parent reply other threads:[~2004-09-27 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 8:52 [PATCH] PCI IRQ resource deallocation support [2/3] Kenji Kaneshige
2004-09-21 14:57 ` [ACPI] " Bjorn Helgaas
2004-09-22 1:24 ` Kenji Kaneshige
2004-09-24 5:52 ` Takayoshi Kochi
2004-09-24 6:29 ` Kenji Kaneshige
2004-09-24 20:39 ` Guennadi Liakhovetski
2004-09-27 5:01 ` Kenji Kaneshige [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=41579EA8.8000700@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=g.liakhovetski@gmx.de \
--cc=greg@kroah.com \
--cc=kaneshige.kenji@soft.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-kochi@bq.jp.nec.com \
--cc=tony.luck@intel.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