summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHaavard Skinnemoen2007-05-13 16:05:59 +0200
committerHaavard Skinnemoen2007-05-13 16:05:59 +0200
commit5d1938c83ca826891a02badef7c9ea8ed57e01a2 (patch)
tree786dfac473eb009547a595f3c8bf3d31d2079b0a
parentLinux 2.6.22-rc1 (diff)
downloadkernel-qcow2-linux-5d1938c83ca826891a02badef7c9ea8ed57e01a2.tar.gz
kernel-qcow2-linux-5d1938c83ca826891a02badef7c9ea8ed57e01a2.tar.xz
kernel-qcow2-linux-5d1938c83ca826891a02badef7c9ea8ed57e01a2.zip
[AVR32] Remove bogus comment in arch/avr32/kernel/irq.c
The comment at the top of arch/avr32/kernel/irq.c doesn't really make sense anymore since most of the actual interrupt handling code is elsewhere. Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
-rw-r--r--arch/avr32/kernel/irq.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/arch/avr32/kernel/irq.c b/arch/avr32/kernel/irq.c
index fd311248c143..61f2de266f62 100644
--- a/arch/avr32/kernel/irq.c
+++ b/arch/avr32/kernel/irq.c
@@ -7,15 +7,6 @@
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
- *
- * This file contains the code used by various IRQ handling routines:
- * asking for different IRQ's should be done through these routines
- * instead of just grabbing them. Thus setups with different IRQ numbers
- * shouldn't result in any weird surprises, and installing new handlers
- * should be easier.
- *
- * IRQ's are in fact implemented a bit like signal handlers for the kernel.
- * Naturally it's not a 1:1 relation, but there are similarities.
*/
#include <linux/interrupt.h>