linux-kernel - [PATCH] : kernel/irq/devres.c:fix kernel-doc

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <499160b0.0e1b6e0a.4589.6461@mx.google.com>
Date:	Tue, 10 Feb 2009 19:10:37 +0800
From:	Qinghuang Feng <qhfeng.kernel@...il.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH] : kernel/irq/devres.c:fix kernel-doc

Fix a typo, change dev_{free|request}_irq to devm_{free|request}_irq.

Signed-off-by: Qinghuang Feng <qhfeng.kernel@...il.com>
---
diff --git a/kernel/irq/devres.c b/kernel/irq/devres.c
index 38a25b8..30b17de 100644
--- a/kernel/irq/devres.c
+++ b/kernel/irq/devres.c
@@ -40,7 +40,7 @@ static int devm_irq_match(struct device *dev, void *res, void *data)
  *	automatically freed on driver detach.
  *
  *	If an IRQ allocated with this function needs to be freed
- *	separately, dev_free_irq() must be used.
+ *	separately, devm_free_irq() must be used.
  */
 int devm_request_irq(struct device *dev, unsigned int irq,
 		     irq_handler_t handler, unsigned long irqflags,
@@ -77,7 +77,7 @@ EXPORT_SYMBOL(devm_request_irq);
  *	Except for the extra @dev argument, this function takes the
  *	same arguments and performs the same function as free_irq().
  *	This function instead of free_irq() should be used to manually
- *	free IRQs allocated with dev_request_irq().
+ *	free IRQs allocated with devm_request_irq().
  */
 void devm_free_irq(struct device *dev, unsigned int irq, void *dev_id)
 {

--
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/