[PATCH 19/25] irq: Remove msi hacks

From: Eric W. Biederman
Date: Tue Jun 20 2006 - 18:29:21 EST


Because of the nasty way that CONFIG_PCI_MSI was implemented
we wound up with set_irq_info and set_native_irq_info, with move_irq and
move_native_irq. Both functions did the same thing but they were
built and called under different circumstances. Now that the msi hacks
are gone we can kill move_irq and set_irq_info.

Signed-off-by: Eric W. Biederman <ebiederm@xxxxxxxxxxxx>
---
include/linux/irq.h | 36 ------------------------------------
1 files changed, 0 insertions(+), 36 deletions(-)

diff --git a/include/linux/irq.h b/include/linux/irq.h
index 6d1ad88..cfd2f31 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -202,36 +202,6 @@ void set_pending_irq(unsigned int irq, c
void move_native_irq(int irq);
void move_masked_irq(int irq);

-#ifdef CONFIG_PCI_MSI
-/*
- * Wonder why these are dummies?
- * For e.g the set_ioapic_affinity_vector() calls the set_ioapic_affinity_irq()
- * counter part after translating the vector to irq info. We need to perform
- * this operation on the real irq, when we dont use vector, i.e when
- * pci_use_vector() is false.
- */
-static inline void move_irq(int irq)
-{
-}
-
-static inline void set_irq_info(int irq, cpumask_t mask)
-{
-}
-
-#else /* CONFIG_PCI_MSI */
-
-static inline void move_irq(int irq)
-{
- move_native_irq(irq);
-}
-
-static inline void set_irq_info(int irq, cpumask_t mask)
-{
- set_native_irq_info(irq, mask);
-}
-
-#endif /* CONFIG_PCI_MSI */
-
#else /* CONFIG_GENERIC_PENDING_IRQ || CONFIG_IRQBALANCE */

static inline void move_irq(int irq)
@@ -250,16 +220,10 @@ static inline void set_pending_irq(unsig
{
}

-static inline void set_irq_info(int irq, cpumask_t mask)
-{
- set_native_irq_info(irq, mask);
-}
-
#endif /* CONFIG_GENERIC_PENDING_IRQ */

#else /* CONFIG_SMP */

-#define move_irq(x)
#define move_native_irq(x)
#define move_masked_irq(x)

--
1.4.0.gc07e

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/