Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754624AbbB0PtN (ORCPT ); Fri, 27 Feb 2015 10:49:13 -0500 Received: from mail-wi0-f173.google.com ([209.85.212.173]:46883 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750777AbbB0PtL (ORCPT ); Fri, 27 Feb 2015 10:49:11 -0500 MIME-Version: 1.0 In-Reply-To: <20150227152435.GA22183@saruman.tx.rr.com> References: <1425043780-21773-1-git-send-email-Valentin.Rothberg@lip6.fr> <20150227152435.GA22183@saruman.tx.rr.com> From: Valentin Rothberg Date: Fri, 27 Feb 2015 16:48:39 +0100 Message-ID: Subject: Re: [PATCH] usb/isp1760: set IRQ flags properly To: balbi@ti.com Cc: Greg KH , laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1135 Lines: 27 On Fri, Feb 27, 2015 at 4:24 PM, Felipe Balbi wrote: > On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote: >> The IRQF_DISABLED is a NOOP and scheduled to be removed. According to >> commit e58aa3d2d0cc (genirq: Run irq handlers with interrupts disabled) >> running IRQ handlers with interrupts enabled can cause stack overflows >> when the interrupt line of the issuing device is still active. >> >> This patch removes using this deprecated flag and additionally removes >> redundantly setting IRQF_SHARED. > > why is it redundant ? It's redundant in the call of isp1760_udc_register() as this function sets the flag by requesting the IRQ. I mistakenly removed it also in the call of isp1760_hcd_register() which does not alter the passed irqflags. I will fix this in a second version of this patch. I am sorry for this mistake. Valentin > -- > balbi -- 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/