From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org
Subject: RE: [ACPI] [PATCH] add acpi_interrupt_to_irq
Date: Thu, 22 Jan 2004 19:08:01 +0000 [thread overview]
Message-ID: <16400.8081.221616.319730@napali.hpl.hp.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC8A2D@hdsmsx402.hd.intel.com>
>>>>> On Thu, 22 Jan 2004 12:41:10 -0500, "Brown, Len" <len.brown@intel.com> said:
Len> Bjorn,
>> irq = acpi_irq_to_vector(irq);
Len> Yeah, this name is totally bogus; and your comments are
Len> absolutely right. I thank you for taking the time to address
Len> it.
Len> When I first saw this I said to myself, "hmm, shouldn't it be
Len> acpi_irq_to_irq()?", nah, that seems even more stupid!";-)
Len> Looks like this is only used for the SCI listed in the FADT.
Len> So maybe we should just call it something like
Len> acpi_fadt_sci_to_irq()?
It would be good to come up with a consistent naming scheme. I/we
tried to do that in the ia64/iosapic.c, but it might need some
updating/revising with recent changes (such as MSIs). Perhaps "gsi"
is also a contender for the ACPI interrupts.
--david
next prev parent reply other threads:[~2004-01-22 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 23:07 [PATCH] add acpi_interrupt_to_irq Bjorn Helgaas
[not found] ` <200401201607.32214.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-01-21 16:39 ` [ACPI] " Bjorn Helgaas
2004-01-21 20:18 ` Bjorn Helgaas
2004-01-21 22:42 ` Nakajima, Jun
[not found] ` <7F740D512C7C1046AB53446D37200173618863-exJ48ZlmiLrcnAH0NVKmOFDQ4js95KgL@public.gmane.org>
2004-01-21 22:54 ` Bjorn Helgaas
2004-01-22 3:36 ` Nakajima, Jun
2004-01-22 16:38 ` Bjorn Helgaas
2004-01-22 17:41 ` Brown, Len
2004-01-22 19:08 ` David Mosberger [this message]
2004-01-23 3:36 ` Nakajima, Jun
[not found] ` <7F740D512C7C1046AB53446D3720017361886A-exJ48ZlmiLrcnAH0NVKmOFDQ4js95KgL@public.gmane.org>
2004-01-23 16:35 ` Bjorn Helgaas
2004-01-23 17:35 ` Nakajima, Jun
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=16400.8081.221616.319730@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=bjorn.helgaas@hp.com \
--cc=jun.nakajima@intel.com \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.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