mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nguyen, Tom L" <tom.l.nguyen@intel.com>
To: <davidm@hpl.hp.com>, "Zwane Mwaikambo" <zwane@linuxpower.ca>
Cc: "long" <tlnguyen@snoqualmie.dp.intel.com>,
	<linux-ia64@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<grep@kroah.com>, <jgarzik@pobox.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Luck, Tony" <tony.luck@intel.com>
Subject: RE: RE[PATCH]2.6.4-rc3 MSI Support for IA64
Date: Fri, 12 Mar 2004 16:22:00 -0800	[thread overview]
Message-ID: <C7AB9DA4D0B1F344BF2489FA165E502404058151@orsmsx404.jf.intel.com> (raw)

On Fri, 12 Mar 2004, David Mosberger wrote:

>>>>> On Fri, 12 Mar 2004 18:26:39 -0500 (EST), Zwane Mwaikambo <zwane@linuxpower.ca> said:

>  Zwane> I wonder if we could consolidate these vector allocators as
>  Zwane> assign_irq_vector(AUTO_ASSIGN) has the same semantics as
>  Zwane> ia64_alloc_vector() and the one for i386 is also almost the
>  Zwane> same as its MSI ilk.

> Agreed.  I don't see any reason why ia64_alloc_vector() and
> assign_irq_vector() couldn't or shouldn't be one and the same thing
> (and assign_irq_vector() is a fine name).

Agree. Thanks!

> Tom, if you want to send me a patch that converts the existing uses of
> ia64_alloc_vector() to assign_irq_vector(), I'd be happy to apply
> (assuming it's clean etc., as usual).

Thanks! We'll do. I will work with Tony and Jun to consolidate i386/IA64 vector 
allocators to ensure it is clean.

Thanks,
Long

             reply	other threads:[~2004-03-13  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13  0:22 Nguyen, Tom L [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-13  1:44 Nakajima, Jun
2004-03-13  0:14 Nguyen, Tom L
2004-03-13  0:08 long
2004-03-12 23:26 ` Zwane Mwaikambo
2004-03-12 23:34   ` David Mosberger
2004-03-12 23:47   ` 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=C7AB9DA4D0B1F344BF2489FA165E502404058151@orsmsx404.jf.intel.com \
    --to=tom.l.nguyen@intel.com \
    --cc=davidm@hpl.hp.com \
    --cc=grep@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlnguyen@snoqualmie.dp.intel.com \
    --cc=tony.luck@intel.com \
    --cc=zwane@linuxpower.ca \
    /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
all inboxes | Powered by JetHome®