summaryrefslogtreecommitdiffstats
path: root/kernel/Kconfig.freezer
diff options
context:
space:
mode:
authorMark Nelson <markn@au1.ibm.com>2008-11-13 11:37:41 +0100
committerIngo Molnar <mingo@elte.hu>2008-11-13 11:59:48 +0100
commit3ff68a6a106c362a6811d3e51bced58e6fc87de7 (patch)
tree9a0a10ff49f7453d26afcced211307c818fd9fa9 /kernel/Kconfig.freezer
parentirq: fix typo (diff)
downloadlinux-3ff68a6a106c362a6811d3e51bced58e6fc87de7.tar.xz
linux-3ff68a6a106c362a6811d3e51bced58e6fc87de7.zip
genirq: __irq_set_trigger: change pr_warning to pr_debug
Commit 0c5d1eb77a8be917b638344a22afe1398236482b (genirq: record trigger type) caused powerpc platforms that had no set_type() function in their struct irq_chip to spew out warnings about "No set_type function for IRQ...". This warning isn't necessarily justified though because the generic powerpc platform code calls set_irq_type() (which in turn calls __irq_set_trigger) with information from the device tree to establish the interrupt mappings, regardless of whether the PIC can actually set a type. A platform's irq_chip might not have a set_type function for a variety of reasons, for example: the platform may have the type essentially hard-coded, or as in the case for Cell interrupts are just messages past around that have no real concept of type, or the platform could even have a virtual PIC as on the PS3. Signed-off-by: Mark Nelson <markn@au1.ibm.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/Kconfig.freezer')
0 files changed, 0 insertions, 0 deletions