From: tip-bot for Geert Uytterhoeven <geert@linux-m68k•org>
To: linux-tip-commits@vger•kernel.org
Cc: linuxppc-dev@lists•ozlabs.org, tglx@linutronix•de,
mingo@redhat•com, geert@linux-m68k•org, hpa@zytor•com
Subject: [tip:irq/urgent] genirq: Fix typo CONFIG_GENIRC_IRQ_SHOW_LEVEL
Date: Mon, 2 May 2011 19:18:57 GMT [thread overview]
Message-ID: <tip-94b2c363dcf732a4edab4ed66041cb36e7f28fbf@git.kernel.org> (raw)
Commit-ID: 94b2c363dcf732a4edab4ed66041cb36e7f28fbf
Gitweb: http://git.kernel.org/tip/94b2c363dcf732a4edab4ed66041cb36e7f28fbf
Author: Geert Uytterhoeven <geert@linux-m68k•org>
AuthorDate: Sat, 30 Apr 2011 22:56:20 +0200
Committer: Thomas Gleixner <tglx@linutronix•de>
CommitDate: Mon, 2 May 2011 21:16:37 +0200
genirq: Fix typo CONFIG_GENIRC_IRQ_SHOW_LEVEL
commit ab7798ffcf98b11a9525cf65bacdae3fd58d357f ("genirq: Expand generic
show_interrupts()") added the Kconfig option GENERIC_IRQ_SHOW_LEVEL to
accomodate PowerPC, but this doesn't actually enable the functionality due
to a typo in the #ifdef check.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Linux/PPC Development <linuxppc-dev@lists•ozlabs.org>
Link: http://lkml.kernel.org/r/%3Calpine.DEB.2.00.1104302251370.19068%40ayla.of.borg%3E
Signed-off-by: Thomas Gleixner <tglx@linutronix•de>
---
kernel/irq/proc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/irq/proc.c b/kernel/irq/proc.c
index dd201bd..834899f 100644
--- a/kernel/irq/proc.c
+++ b/kernel/irq/proc.c
@@ -419,7 +419,7 @@ int show_interrupts(struct seq_file *p, void *v)
} else {
seq_printf(p, " %8s", "None");
}
-#ifdef CONFIG_GENIRC_IRQ_SHOW_LEVEL
+#ifdef CONFIG_GENERIC_IRQ_SHOW_LEVEL
seq_printf(p, " %-8s", irqd_is_level_type(&desc->irq_data) ? "Level" : "Edge");
#endif
if (desc->name)
reply other threads:[~2011-05-02 19:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-94b2c363dcf732a4edab4ed66041cb36e7f28fbf@git.kernel.org \
--to=geert@linux-m68k$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-tip-commits@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@redhat$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox