Commit ee5ac9dd authored by Stephen Rothwell's avatar Stephen Rothwell Committed by David S. Miller

[SPARC]: device_node name constification fallout

A couple of routines need their arguments to be const.
Signed-off-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 3e4d2650
...@@ -25,7 +25,7 @@ ...@@ -25,7 +25,7 @@
struct linux_ebus *ebus_chain = NULL; struct linux_ebus *ebus_chain = NULL;
/* We are together with pcic.c under CONFIG_PCI. */ /* We are together with pcic.c under CONFIG_PCI. */
extern unsigned int pcic_pin_to_irq(unsigned int, char *name); extern unsigned int pcic_pin_to_irq(unsigned int, const char *name);
/* /*
* IRQ Blacklist * IRQ Blacklist
...@@ -69,7 +69,7 @@ static inline unsigned long ebus_alloc(size_t size) ...@@ -69,7 +69,7 @@ static inline unsigned long ebus_alloc(size_t size)
/* /*
*/ */
int __init ebus_blacklist_irq(char *name) int __init ebus_blacklist_irq(const char *name)
{ {
struct ebus_device_irq *dp; struct ebus_device_irq *dp;
......
...@@ -37,8 +37,6 @@ ...@@ -37,8 +37,6 @@
#include <asm/irq_regs.h> #include <asm/irq_regs.h>
unsigned int pcic_pin_to_irq(unsigned int pin, char *name);
/* /*
* I studied different documents and many live PROMs both from 2.30 * I studied different documents and many live PROMs both from 2.30
* family and 3.xx versions. I came to the amazing conclusion: there is * family and 3.xx versions. I came to the amazing conclusion: there is
...@@ -681,7 +679,7 @@ void __devinit pcibios_fixup_bus(struct pci_bus *bus) ...@@ -681,7 +679,7 @@ void __devinit pcibios_fixup_bus(struct pci_bus *bus)
* pcic_pin_to_irq() is exported to ebus.c. * pcic_pin_to_irq() is exported to ebus.c.
*/ */
unsigned int unsigned int
pcic_pin_to_irq(unsigned int pin, char *name) pcic_pin_to_irq(unsigned int pin, const char *name)
{ {
struct linux_pcic *pcic = &pcic0; struct linux_pcic *pcic = &pcic0;
unsigned int irq; unsigned int irq;
......
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