From: Henne <henne@nachtwindheim.de>
To: mingo@redhead.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] [DOC] kerneldoc for handle_bad_irq()
Date: Tue, 29 Aug 2006 13:11:08 +0200 [thread overview]
Message-ID: <44F420CC.4010608@nachtwindheim.de> (raw)
From: Henrik Kretzschmar <henne@nachtwindheim.de>
Adds the description of the parameters from handle_bad_irq().
That should be merged before 2.6.18 release.
Signed-off-by: Henrik Kretzschmar <henne@nachtwindheim.de>
---
diff -ruN linux-2.6.18-rc2/kernel/irq/handle.c linux/kernel/irq/handle.c
--- linux-2.6.18-rc2/kernel/irq/handle.c 2006-07-18 13:37:39.000000000 +0200
+++ linux/kernel/irq/handle.c 2006-07-18 13:51:15.000000000 +0200
@@ -20,6 +20,11 @@
/**
* handle_bad_irq - handle spurious and unhandled irqs
+ * @irq: the interrupt number
+ * @desc: description of the interrupt
+ * @regs: pointer to a register structure
+ *
+ * Handles spurious and unhandled IRQ's. It also prints a debugmessage.
*/
void fastcall
handle_bad_irq(unsigned int irq, struct irq_desc *desc, struct pt_regs *regs)
reply other threads:[~2006-08-29 11:10 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=44F420CC.4010608@nachtwindheim.de \
--to=henne@nachtwindheim.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhead.com \
/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