From: Breno Leitão Date: Thu, 24 Sep 2009 19:58:22 +0000 (-0300) Subject: jsm: IRQ handlers doesn't need to have IRQ_DISABLED enabled X-Git-Tag: accepted/tizen/common/20141203.182822~13518^2~57 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a88a477f1df703f0e2a7592e19618799cb598623;p=platform%2Fkernel%2Flinux-arm64.git jsm: IRQ handlers doesn't need to have IRQ_DISABLED enabled Currently jsm is showing the following message when loaded: IRQ 432/JSM: IRQF_DISABLED is not guaranteed on shared IRQs It's because the request_irq() is called using IRQF_DISABLED and IRQF_SHARED. Actually there is no need to use IRQF_DISABLED in this driver. Signed-off-by: Breno Leitão Cc: Scott Kilau Signed-off-by: Andrew Morton Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/serial/jsm/jsm_driver.c b/drivers/serial/jsm/jsm_driver.c index b3604aa..48326f7 100644 --- a/drivers/serial/jsm/jsm_driver.c +++ b/drivers/serial/jsm/jsm_driver.c @@ -123,7 +123,7 @@ static int __devinit jsm_probe_one(struct pci_dev *pdev, const struct pci_device } rc = request_irq(brd->irq, brd->bd_ops->intr, - IRQF_DISABLED|IRQF_SHARED, "JSM", brd); + IRQF_SHARED, "JSM", brd); if (rc) { printk(KERN_WARNING "Failed to hook IRQ %d\n",brd->irq); goto out_iounmap;