public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@linux-foundation.org, mingo@elte.hu,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 5/5] Introduce "used_vectors" bitmap which can be used to reserve vectors.
Date: Wed, 17 Oct 2007 14:35:36 -0700	[thread overview]
Message-ID: <20071017143536.f4e7cba1.akpm@linux-foundation.org> (raw)
In-Reply-To: <200710172056.05123.rusty@rustcorp.com.au>

On Wed, 17 Oct 2007 20:56:04 +1000
Rusty Russell <rusty@rustcorp.com.au> wrote:

> This simplifies the io_apic.c __assign_irq_vector() logic and removes
> the explicit SYSCALL_VECTOR check, and also allows for vectors to be
> reserved by other mechanisms (ie. lguest).

I already have this one as
x86_64-mm-introduce-used_vectors-bitmap-which-can-be-used-to-reserve-vectors.patch
- part of the firstfloor tree.

Thomas is going through those patches and is getting them merged up - a large
batch went through today.

So I assume he'll me merging this patch via that route, unless he has
decided to skip it for some reason.

Either way, I guess I'll hang onto the firstfloor.org leftovers until each
one has some sort of definite disposition.


  reply	other threads:[~2007-10-17 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200710172046.55454.rusty@rustcorp.com.au>
     [not found] ` <200710172052.47230.rusty@rustcorp.com.au>
     [not found]   ` <200710172054.45652.rusty@rustcorp.com.au>
2007-10-17 10:56     ` [PATCH 5/5] Introduce "used_vectors" bitmap which can be used to reserve vectors Rusty Russell
2007-10-17 21:35       ` Andrew Morton [this message]
2007-10-17 21:42         ` Thomas Gleixner

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=20071017143536.f4e7cba1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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