From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: lockdep and threaded IRQs (was: ...) Date: Mon, 02 Mar 2009 14:16:10 +0100 Message-ID: <1235999770.5330.367.camel@laptop> References: <1235762883-20870-1-git-send-email-me@felipebalbi.com> <200902271350.32380.david-b@pacbell.net> <20090227140907.f159be9b.akpm@linux-foundation.org> <200902271518.58246.david-b@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:41475 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750920AbZCBNQ0 (ORCPT ); Mon, 2 Mar 2009 08:16:26 -0500 In-Reply-To: <200902271518.58246.david-b@pacbell.net> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: David Brownell Cc: Andrew Morton , me@felipebalbi.com, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, felipe.balbi@nokia.com, dmitry.torokhov@gmail.com, sameo@openedhand.com, tglx@linutronix.de On Fri, 2009-02-27 at 15:18 -0800, David Brownell wrote: > > This stuff just pokes at some annoying current gaps in the > IRQ framework. I'll be glad when eventually there's no > need to work around those weaknesses ... that is, when > real threaded IRQ support is available. Its unfortunate that you prefer these dinky little hacks over helping out providing whatever infrastructure you need. There's plenty good reasons for mandating that irq handlers run with irqs disabled, if you need threaded handlers -- that's fine, but then teach the generic code about them. What you do _NOT_ do is hack your way around things, that's not how Linux works, and by doing that you make the world a slightly worse place for everyone.