lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 07 Aug 2014 18:48:21 +0200 From: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com> To: Samuel Ortiz <sameo@...ux.intel.com> Cc: Lee Jones <lee.jones@...aro.org>, Krzysztof Kozlowski <k.kozlowski@...sung.com>, Sangbeom Kim <sbkim73@...sung.com>, Kyungmin Park <kyungmin.park@...sung.com>, linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org Subject: Re: [PATCH] mfd: sec-irq: fix support for devices without irq specified [ added missing linux-samsung-soc ML, sorry for the noise ] On Thursday, August 07, 2014 06:42:28 PM Bartlomiej Zolnierkiewicz wrote: > Add missing check for the case of device without irq specified > in sec_irq_exit() (please note that sec_irq_init() already > correctly handles such devices). > > This is needed for Insignal's Exynos4412 based Origen board. > > Cc: Krzysztof Kozlowski <k.kozlowski@...sung.com> > Cc: Sangbeom Kim <sbkim73@...sung.com> > Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com> > Acked-by: Kyungmin Park <kyungmin.park@...sung.com> > --- > patch is against next-20140804 branch of linux-next kernel > > drivers/mfd/sec-irq.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/mfd/sec-irq.c b/drivers/mfd/sec-irq.c > index f9a5786..b65a7f0 100644 > --- a/drivers/mfd/sec-irq.c > +++ b/drivers/mfd/sec-irq.c > @@ -478,5 +478,6 @@ int sec_irq_init(struct sec_pmic_dev *sec_pmic) > > void sec_irq_exit(struct sec_pmic_dev *sec_pmic) > { > - regmap_del_irq_chip(sec_pmic->irq, sec_pmic->irq_data); > + if (sec_pmic->irq) > + regmap_del_irq_chip(sec_pmic->irq, sec_pmic->irq_data); > } -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists