From: Karsten Keil <isdn@linux-pingi.de>
To: Andreas Mohr <andi@lisas.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mISDN GIT: hfcpci cleanup failure on IRQ weirdness
Date: Tue, 2 Jun 2009 17:29:58 +0200 [thread overview]
Message-ID: <200906021729.58677.isdn@linux-pingi.de> (raw)
In-Reply-To: <20090602130649.GA14794@rhlx01.hs-esslingen.de>
Hi Andreas,
On Dienstag, 2. Juni 2009 15:06:49 Andreas Mohr wrote:
Thanks for discovering this issue.
...
> ChangeLog:
> Make sure to properly bail out (call free_irq())
> after hfcpci interrupt detection failure.
> Improve comment.
>
> Signed-off-by: Andreas Mohr <andi@lisas.de>
>
> --- ./drivers/isdn/hardware/mISDN/hfcpci.c.orig 2009-06-02
> 13:54:10.000000000 +0200 +++
> ./drivers/isdn/hardware/mISDN/hfcpci.c 2009-06-02 14:29:20.000000000 +0200
> @@ -1172,7 +1172,7 @@ hfcpci_int(int intno, void *dev_id)
> printk(KERN_DEBUG
> "HFC-PCI: stat(%02x) s1(%02x)\n", stat, val);
> } else {
> - /* shared */
> + /* (shared) IRQ triggered by other device */
> spin_unlock(&hc->lock);
> return IRQ_NONE;
> }
Hmm, I think shared as comment in the IRQ function should be
enough - but I do not complain to a longer comment.
> @@ -1807,8 +1807,7 @@ init_card(struct hfc_pci *hc)
> "HFC PCI: IRQ(%d) getting no interrupts "
> "during init %d\n", hc->irq, 4 - cnt);
> if (cnt == 1) {
> - spin_unlock_irqrestore(&hc->lock, flags);
> - return -EIO;
> + goto fail;
> } else {
> reset_hfcpci(hc);
> cnt--;
easier:
if (cnt == 1)
break;
else {
I will send this patch together with some other ISDN fixes again soon.
Karsten
next prev parent reply other threads:[~2009-06-02 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 13:06 [PATCH] mISDN GIT: hfcpci cleanup failure on IRQ weirdness Andreas Mohr
2009-06-02 14:02 ` Andreas Mohr
2009-06-02 14:53 ` Karsten Keil
2009-06-02 15:44 ` Andreas Mohr
2009-06-02 15:29 ` Karsten Keil [this message]
2009-06-02 15:46 ` Andreas Mohr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906021729.58677.isdn@linux-pingi.de \
--to=isdn@linux-pingi.de \
--cc=andi@lisas.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox