genirq: Fix handle_bad_irq kerneldoc comment

[firefly-linux-kernel-4.4.55.git] / Documentation / gpio / driver.txt

diff --git a/Documentation/gpio/driver.txt b/Documentation/gpio/driver.txt
index 31e0b5db55d89a1e1d9e8da5e9f3fef2a4694450..90d0f6aba7a6848a3043ff7a7de3913118a98461 100644 (file)
--- a/Documentation/gpio/driver.txt
+++ b/Documentation/gpio/driver.txt
@@ -158,12 +158,12 @@ Locking IRQ usage
 Input GPIOs can be used as IRQ signals. When this happens, a driver is requested
 to mark the GPIO as being used as an IRQ:
 
-       int gpio_lock_as_irq(struct gpio_chip *chip, unsigned int offset)
+       int gpiochip_lock_as_irq(struct gpio_chip *chip, unsigned int offset)
 
 This will prevent the use of non-irq related GPIO APIs until the GPIO IRQ lock
 is released:
 
-       void gpio_unlock_as_irq(struct gpio_chip *chip, unsigned int offset)
+       void gpiochip_unlock_as_irq(struct gpio_chip *chip, unsigned int offset)
 
 When implementing an irqchip inside a GPIO driver, these two functions should
 typically be called in the .startup() and .shutdown() callbacks from the