Commit e85f008d authored by Robert P. J. Day's avatar Robert P. J. Day Committed by Paul Mackerras

[POWERPC] Correct apparently misspelled "XMON" preprocessor symbol.

Correct the apparent misspelling of "XMON" to "CONFIG_XMON".
Signed-off-by: default avatarRobert P. J. Day <rpjday@mindspring.com>
Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
parent 7850ad5c
...@@ -427,7 +427,7 @@ static void __init chrp_find_openpic(void) ...@@ -427,7 +427,7 @@ static void __init chrp_find_openpic(void)
of_node_put(np); of_node_put(np);
} }
#if defined(CONFIG_VT) && defined(CONFIG_INPUT_ADBHID) && defined(XMON) #if defined(CONFIG_VT) && defined(CONFIG_INPUT_ADBHID) && defined(CONFIG_XMON)
static struct irqaction xmon_irqaction = { static struct irqaction xmon_irqaction = {
.handler = xmon_irq, .handler = xmon_irq,
.mask = CPU_MASK_NONE, .mask = CPU_MASK_NONE,
...@@ -493,7 +493,7 @@ static void __init chrp_find_8259(void) ...@@ -493,7 +493,7 @@ static void __init chrp_find_8259(void)
void __init chrp_init_IRQ(void) void __init chrp_init_IRQ(void)
{ {
#if defined(CONFIG_VT) && defined(CONFIG_INPUT_ADBHID) && defined(XMON) #if defined(CONFIG_VT) && defined(CONFIG_INPUT_ADBHID) && defined(CONFIG_XMON)
struct device_node *kbd; struct device_node *kbd;
#endif #endif
chrp_find_openpic(); chrp_find_openpic();
...@@ -510,7 +510,7 @@ void __init chrp_init_IRQ(void) ...@@ -510,7 +510,7 @@ void __init chrp_init_IRQ(void)
if (_chrp_type == _CHRP_Pegasos) if (_chrp_type == _CHRP_Pegasos)
ppc_md.get_irq = i8259_irq; ppc_md.get_irq = i8259_irq;
#if defined(CONFIG_VT) && defined(CONFIG_INPUT_ADBHID) && defined(XMON) #if defined(CONFIG_VT) && defined(CONFIG_INPUT_ADBHID) && defined(CONFIG_XMON)
/* see if there is a keyboard in the device tree /* see if there is a keyboard in the device tree
with a parent of type "adb" */ with a parent of type "adb" */
for (kbd = find_devices("keyboard"); kbd; kbd = kbd->next) for (kbd = find_devices("keyboard"); kbd; kbd = kbd->next)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment