public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: long <tlnguyen@snoqualmie.dp.intel.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
	jun.nakajima@intel.com, tom.l.nguyen@intel.com,
	tony.luck@intel.com
Subject: Re: [PATCH]2.6.3-rc2 MSI Support for IA64
Date: Fri, 20 Feb 2004 17:54:44 +0100	[thread overview]
Message-ID: <jeeksp4ror.fsf@sykes.suse.de> (raw)
In-Reply-To: <200402201747.i1KHlnqU005488@snoqualmie.dp.intel.com> (long's message of "Fri, 20 Feb 2004 09:47:49 -0800")

long <tlnguyen@snoqualmie.dp.intel.com> writes:

> @@ -316,6 +310,19 @@
>  	return current_vector;
>  }
>  
> +int ia64_alloc_vector(void)
> +{
> +	static int next_vector = IA64_FIRST_DEVICE_VECTOR;
> +
> +	if (next_vector > IA64_LAST_DEVICE_VECTOR)
> +		/* XXX could look for sharable vectors instead of panic'ing... */
> +		panic("ia64_alloc_vector: out of interrupt vectors!");
> +
> +	nr_alloc_vectors++;
> +
> +	return next_vector++;
> +}
> +

IMHO this should be CONFIG_IA64 only.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2004-02-20 16:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 17:47 [PATCH]2.6.3-rc2 MSI Support for IA64 long
2004-02-20 16:54 ` Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-20 18:36 Nguyen, Tom L
2004-02-20 18:58 ` Mika Penttilä
2004-02-20 19:05 ` David Mosberger
2004-02-21  1:55 ` Zwane Mwaikambo
2004-02-20 19:31 Nguyen, Tom L
2004-02-20 19:43 ` Mika Penttilä
2004-02-20 19:38 Nguyen, Tom L
2004-02-23 16:44 Nguyen, Tom L

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=jeeksp4ror.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=greg@kroah.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlnguyen@snoqualmie.dp.intel.com \
    --cc=tom.l.nguyen@intel.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