From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [patch 1/2] genirq: Run irq handlers with interrupts disabled Date: Fri, 26 Mar 2010 07:13:10 +0100 Message-ID: <20100326061310.GV20695@one.firstfloor.org> References: <20100326000325.917127328@linutronix.de> <20100326000405.758579387@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from one.firstfloor.org ([213.235.205.2]:55114 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753676Ab0CZGNM (ORCPT ); Fri, 26 Mar 2010 02:13:12 -0400 Content-Disposition: inline In-Reply-To: <20100326000405.758579387@linutronix.de> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Thomas Gleixner Cc: Linus Torvalds , LKML , linux-arch@vger.kernel.org, Andrew Morton , Ingo Molnar , Peter Zijlstra , Alan Cox , Andi Kleen , David Miller , Greg Kroah-Hartman , Arnaldo Carvalho de Melo > Drivers for whacky hardware still can reenable them in the handler > itself, if the need arises. (They do already due to lockdep) Can you please explain that lockdep reference? I don't think lockdep really forces on interrupts, does it? BTW the one problem I have with this patchkit is that it's clearly no stable candidate and I was hoping for a stable fix too. Any chance to at least approve my original patch for .32/.33 only? -Andi -- ak@linux.intel.com -- Speaking for myself only.