The function __irq_complete_move() was merged into irq_complete_move()
by commit e027fffff799 ("x86/irq: Unbreak interrupt affinity setting"),
which removed the separate static helper and consolidated the logic into
the public function. Update the comment in fixup_irqs() accordingly.
Signed-off-by: kexinsun <kexinsun@smail.nju.edu.cn>
---
arch/x86/kernel/apic/vector.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/apic/vector.c b/arch/x86/kernel/apic/vector.c
index bddc54465399..36338f264bae 100644
--- a/arch/x86/kernel/apic/vector.c
+++ b/arch/x86/kernel/apic/vector.c
@@ -946,7 +946,7 @@ static void apic_force_complete_move(struct irq_data *irqd)
* -EBUSY. This can leave the interrupt in a stale state.
*
* All CPUs are stuck in stop machine with interrupts disabled so
- * calling __irq_complete_move() would be completely pointless.
+ * calling irq_complete_move() would be completely pointless.
*
* 1) The interrupt is in move_in_progress state. That means that we
* have not seen an interrupt since the io_apic was reprogrammed to
--
2.25.1