public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>,
	acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org
Cc: "Brown, Len" <len.brown@intel.com>
Subject: Re: [ACPI] [PATCH] add acpi_interrupt_to_irq
Date: Thu, 22 Jan 2004 09:38:18 -0700	[thread overview]
Message-ID: <200401220938.18951.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173618864@scsmsx402.sc.intel.com>

On Wednesday 21 January 2004 8:36 pm, Nakajima, Jun wrote:

> > 	(b) is "acpi_interrupt_to_irq" a better name than
> > 	    "acpi_irq_to_vector"?
> 
> I don't know what people imagine by "interrupt", but to me it implies an
> "event". 

Are you saying that you think "acpi_irq_to_vector" is the right name?
What does "vector" mean?  The return value of that function is in
fact a Linux IRQ, and is passed to request_irq() and free_irq().  So
I think the correct name is "acpi_SOMETHING_to_irq".  If you don't
like "interrupt", you can propose something else.  I just think it's
misleading for the name to contain "to_vector", when it's really
doing "to_irq".



  reply	other threads:[~2004-01-22 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  3:36 [PATCH] add acpi_interrupt_to_irq Nakajima, Jun
2004-01-22 16:38 ` Bjorn Helgaas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-22 17:41 [ACPI] " Brown, Len
2004-01-22 19:08 ` David Mosberger
2004-01-21 22:42 Nakajima, Jun
2004-01-20 23:07 Bjorn Helgaas
2004-01-21 16:39 ` Bjorn Helgaas
2004-01-21 20:18   ` [ACPI] " Bjorn Helgaas

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=200401220938.18951.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --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