Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750796AbWITBE5 (ORCPT ); Tue, 19 Sep 2006 21:04:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750797AbWITBE5 (ORCPT ); Tue, 19 Sep 2006 21:04:57 -0400 Received: from mga07.intel.com ([143.182.124.22]:49005 "EHLO azsmga101.ch.intel.com") by vger.kernel.org with ESMTP id S1750796AbWITBE5 (ORCPT ); Tue, 19 Sep 2006 21:04:57 -0400 X-ExtLoop1: 1 X-IronPort-AV: i="4.09,187,1157353200"; d="scan'208"; a="119293661:sNHT988085987" Message-ID: <451093A5.20800@linux.intel.com> Date: Wed, 20 Sep 2006 09:04:37 +0800 From: Arjan van de Ven User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Andrew Morton CC: Peter Zijlstra , Ayaz Abdulla , linux-kernel , Jeff Garzik , Ingo Molnar , Dave Jones Subject: Re: [PATCH] forcedeth: hardirq lockdep warning References: <1158670522.3278.13.camel@taijtu> <20060919111448.9274c699.akpm@osdl.org> In-Reply-To: <20060919111448.9274c699.akpm@osdl.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 579 Lines: 13 > That's "fix deadlock", not "fix lockdep warning". However it's often the > case that it's not really deadlockable because (often) the card's IRQ line > has been disabled. That appears to be the case in nv_do_nic_poll()'s call > to nv_nic_irq_tx, for example. > except when it's a shared irq line, then the game rules changed ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/