aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2008-10-15 08:31:29 -0400
committerIngo Molnar <mingo@elte.hu>2008-10-16 10:53:14 -0400
commitc6b7674f323622d86316bf7951ad9cae1ce24642 (patch)
tree00ff8c061f9c0822c56e46bc59c46dced278f9a9 /kernel
parent70dd4d992ab324a59cdcd6bedc3f4e729863d514 (diff)
genirq: use inline function for irq_to_desc
For the non sparse irq case an inline function is perfectly fine. Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'kernel')
-rw-r--r--kernel/irq/handle.c14
1 files changed, 0 insertions, 14 deletions
diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
index fb6bdb602a93..c19896f895f9 100644
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@ -262,20 +262,6 @@ struct irq_desc irq_desc[NR_IRQS] __cacheline_aligned_in_smp = {
262 262
263#endif 263#endif
264 264
265#ifndef CONFIG_HAVE_SPARSE_IRQ
266struct irq_desc *irq_to_desc(unsigned int irq)
267{
268 if (irq < nr_irqs)
269 return &irq_desc[irq];
270
271 return NULL;
272}
273struct irq_desc *irq_to_desc_alloc(unsigned int irq)
274{
275 return irq_to_desc(irq);
276}
277#endif
278
279/* 265/*
280 * What should we do if we get a hw irq event on an illegal vector? 266 * What should we do if we get a hw irq event on an illegal vector?
281 * Each architecture has to answer this themself. 267 * Each architecture has to answer this themself.