From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mips@linux-mips.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] dz.c: Don't panic() when request_irq() fails
Date: Fri, 19 Oct 2007 21:24:16 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64N.0710192119360.13279@blysk.ds.pg.gda.pl> (raw)
Well, panic() is a little bit undue if request_irq() fails; there is
probably no need to justify it any further. Handle the case gracefully,
by unregistering the driver.
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
---
Tested with checkpatch.pl and at the run-time -- MIPS/Linux on a
DECstation 5000/200.
Please apply,
Maciej
patch-mips-2.6.18-20060920-dz-init-0
diff -up --recursive --new-file linux-mips-2.6.18-20060920.macro/drivers/serial/dz.c linux-mips-2.6.18-20060920/drivers/serial/dz.c
--- linux-mips-2.6.18-20060920.macro/drivers/serial/dz.c 2006-11-23 05:17:01.000000000 +0000
+++ linux-mips-2.6.18-20060920/drivers/serial/dz.c 2007-01-14 00:39:20.000000000 +0000
@@ -795,18 +795,28 @@ static int __init dz_init(void)
dz_reset(&dz_ports[0]);
#endif
- if (request_irq(dz_ports[0].port.irq, dz_interrupt,
- IRQF_DISABLED, "DZ", &dz_ports[0]))
- panic("Unable to register DZ interrupt");
-
ret = uart_register_driver(&dz_reg);
if (ret != 0)
- return ret;
+ goto out;
+
+ ret = request_irq(dz_ports[0].port.irq, dz_interrupt, IRQF_DISABLED,
+ "DZ", &dz_ports[0]);
+ if (ret != 0) {
+ printk(KERN_ERR "dz: Cannot get IRQ %d!\n",
+ dz_ports[0].port.irq);
+ goto out_unregister;
+ }
for (i = 0; i < DZ_NB_PORT; i++)
uart_add_one_port(&dz_reg, &dz_ports[i].port);
return ret;
+
+out_unregister:
+ uart_unregister_driver(&dz_reg);
+
+out:
+ return ret;
}
module_init(dz_init);
reply other threads:[~2007-10-19 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64N.0710192119360.13279@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).