From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759876Ab2HJKFB (ORCPT ); Fri, 10 Aug 2012 06:05:01 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:56528 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759670Ab2HJKE7 (ORCPT ); Fri, 10 Aug 2012 06:04:59 -0400 Date: Fri, 10 Aug 2012 11:04:57 +0100 From: Mark Brown To: Feng Tang Cc: Axel Lin , linux-kernel@vger.kernel.org, Fengguang Wu Subject: Re: [PATCH] wm831x-dcdc: fix coccinelle warnings of missing IRQF_ONESHOT Message-ID: <20120810100456.GF24328@opensource.wolfsonmicro.com> References: <1344560304-4322-1-git-send-email-feng.tang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1344560304-4322-1-git-send-email-feng.tang@intel.com> X-Cookie: Be different: conform. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 10, 2012 at 08:58:24AM +0800, Feng Tang wrote: > From: Fengguang Wu > > /c/kernel-tests/src/linux/drivers/regulator/wm831x-dcdc.c:829:7-27: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT > /c/kernel-tests/src/linux/drivers/regulator/wm831x-dcdc.c:695:7-27: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT > /c/kernel-tests/src/linux/drivers/regulator/wm831x-dcdc.c:533:7-27: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT > /c/kernel-tests/src/linux/drivers/regulator/wm831x-dcdc.c:542:7-27: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT > Generated by: scripts/coccinelle/misc/irqf_oneshot.cocci > Make sure threaded IRQs without a primary handler are always request with > IRQF_ONESHOT This is actually a false positive - _ONESHOT is only needed for interrupts without a primary handler if the interrupt controller is not threaded. For this driver (and most of the other wm831x drivers, as well as many other MFDs) we are guaranteed that the primary handler can never be called. It's not going to hurt, though.