From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: [patch 2.6.17] s2io driver irq fix Date: Thu, 22 Jun 2006 22:54:23 -0700 Message-ID: References: <20060621211534.b740d0f8.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ananda Raju , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, dgc@sgi.com, balbir@in.ibm.com, viro@zeniv.linux.org.uk, neilb@suse.de, jblunck@suse.de, tglx@linutronix.de, leonid.grossman@neterion.com, ravinandan.arakali@neterion.com, alicia.pena@neterion.com Return-path: Received: from sj-iport-4.cisco.com ([171.68.10.86]:21379 "EHLO sj-iport-4.cisco.com") by vger.kernel.org with ESMTP id S932323AbWFWFy0 (ORCPT ); Fri, 23 Jun 2006 01:54:26 -0400 To: Andrew Morton In-Reply-To: <20060621211534.b740d0f8.akpm@osdl.org> (Andrew Morton's message of "Wed, 21 Jun 2006 21:15:34 -0700") Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Andrew> Is it usual to prohibit IRQ sharing with msix? With current code at least, MSI/MSI-X interrupts can never be shared. - R.