From: Glauber Costa <gcosta@redhat.com>
To: Amit Shah <amit.shah@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] use NR_IRQS for irq count
Date: Wed, 09 Apr 2008 09:11:10 -0300 [thread overview]
Message-ID: <47FCB25E.1070606@redhat.com> (raw)
In-Reply-To: <200804091013.11149.amit.shah@qumranet.com>
Amit Shah wrote:
> * On Tuesday 08 April 2008 22:34:36 Glauber Costa wrote:
>> Instead of artificially limiting irq numbers, use arch provided NR_IRQS
>>
>> Signed-off-by: Glauber Costa <gcosta@redhat.com>
>
> Thanks, applied.
>
> Going forward, we're going to use the in-kernel approach for interrupt
> injection (which already has this change). The irqhook module will stay
> around for testing / debugging purposes (will be used with -no-kvm-irqchip).
>
> Amit.
Is it already in your tree?
next prev parent reply other threads:[~2008-04-09 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 17:04 [PATCH] use NR_IRQS for irq count Glauber Costa
2008-04-09 4:43 ` Amit Shah
[not found] ` <200804091013.11149.amit.shah@qumranet.com>
2008-04-09 12:11 ` Glauber Costa [this message]
2008-04-10 9:11 ` Amit Shah
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=47FCB25E.1070606@redhat.com \
--to=gcosta@redhat.com \
--cc=amit.shah@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).