linux-kernel - [PATCH] genirq: update the comment for generic_handle_irq

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]

Date:	Tue,  1 Sep 2015 10:35:50 +0800
From:	Huang Shijie <shijie.huang@....com>
To:	tglx@...utronix.de
Cc:	jiang.liu@...ux.intel.com, peterz@...radead.org,
	rafael.j.wysocki@...el.com, jason@...edaemon.net,
	marc.zyngier@....com, linux-kernel@...r.kernel.org,
	Huang Shijie <shijie.huang@....com>
Subject: [PATCH] genirq: update the comment for generic_handle_irq_desc

The __do_IRQ() is removed by the patch:
      "1c77ff2 genirq: Remove __do_IRQ"

This patch updates the comment for generic_handle_irq_desc().

Signed-off-by: Huang Shijie <shijie.huang@....com>
---
 include/linux/irqdesc.h | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/include/linux/irqdesc.h b/include/linux/irqdesc.h
index 5acfa26..0593c69 100644
--- a/include/linux/irqdesc.h
+++ b/include/linux/irqdesc.h
@@ -137,9 +137,7 @@ static inline struct msi_desc *irq_desc_get_msi_desc(struct irq_desc *desc)
 
 /*
  * Architectures call this to let the generic IRQ layer
- * handle an interrupt. If the descriptor is attached to an
- * irqchip-style controller then we call the ->handle_irq() handler,
- * and it calls __do_IRQ() if it's attached to an irqtype-style controller.
+ * handle an interrupt.
  */
 static inline void generic_handle_irq_desc(unsigned int irq, struct irq_desc *desc)
 {
-- 
2.1.4

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