linux-kernel - [PATCH][linux-next] genirq: Fix warning while make xmldocs caused by chip.c

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: <1438164576-5945-1-git-send-email-standby24x7@gmail.com>
Date:	Wed, 29 Jul 2015 19:09:36 +0900
From:	Masanari Iida <standby24x7@...il.com>
To:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org
Cc:	Masanari Iida <standby24x7@...il.com>
Subject: [PATCH][linux-next] genirq: Fix warning while make xmldocs caused by chip.c

This patch fix following warning while make xmldocs.

Warning(.//kernel/irq/chip.c:1009): No description found
for parameter 'vcpu_info'
Warning(.//kernel/irq/chip.c:1009): Excess function parameter
'dest' description in 'irq_chip_set_vcpu_affinity_parent'

Signed-off-by: Masanari Iida <standby24x7@...il.com>
---
 kernel/irq/chip.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 76f199d..09304a6 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -1003,7 +1003,7 @@ int irq_chip_retrigger_hierarchy(struct irq_data *data)
 /**
  * irq_chip_set_vcpu_affinity_parent - Set vcpu affinity on the parent interrupt
  * @data:	Pointer to interrupt specific data
- * @dest:	The vcpu affinity information
+ * @vcpu_info:	The vcpu affinity information
  */
 int irq_chip_set_vcpu_affinity_parent(struct irq_data *data, void *vcpu_info)
 {
-- 
2.5.0

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