linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 4/7] gpio: acpi: Fixup kerneldoc
Date: Mon, 24 Jul 2017 16:57:25 +0200	[thread overview]
Message-ID: <20170724145728.7662-4-thierry.reding@gmail.com> (raw)
In-Reply-To: <20170724145728.7662-1-thierry.reding@gmail.com>

From: Thierry Reding <treding@nvidia.com>

Fix up a parameter description to match the code and fix markup for a
constant to prettify output.

Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 drivers/gpio/gpiolib-acpi.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
index c9b42dd12dfa..4d2113530735 100644
--- a/drivers/gpio/gpiolib-acpi.c
+++ b/drivers/gpio/gpiolib-acpi.c
@@ -61,7 +61,7 @@ static int acpi_gpiochip_find(struct gpio_chip *gc, void *data)
 #ifdef CONFIG_PINCTRL
 /**
  * acpi_gpiochip_pin_to_gpio_offset() - translates ACPI GPIO to Linux GPIO
- * @chip: GPIO chip
+ * @gdev: GPIO device
  * @pin: ACPI GPIO pin number from GpioIo/GpioInt resource
  *
  * Function takes ACPI GpioIo/GpioInt pin number as a parameter and
@@ -763,7 +763,7 @@ struct gpio_desc *acpi_node_get_gpiod(struct fwnode_handle *fwnode,
  * The function is idempotent, though each time it runs it will configure GPIO
  * pin direction according to the flags in GpioInt resource.
  *
- * Return: Linux IRQ number (>%0) on success, negative errno on failure.
+ * Return: Linux IRQ number (> %0) on success, negative errno on failure.
  */
 int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index)
 {
-- 
2.13.3


  parent reply	other threads:[~2017-07-24 14:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 14:57 [PATCH 1/7] gpio: Cleanup kerneldoc Thierry Reding
2017-07-24 14:57 ` [PATCH 2/7] gpio: of: Improve kerneldoc Thierry Reding
2017-08-02 12:07   ` Linus Walleij
2017-07-24 14:57 ` [PATCH 3/7] gpio: devres: " Thierry Reding
2017-08-02 12:07   ` Linus Walleij
2017-07-24 14:57 ` Thierry Reding [this message]
2017-07-24 15:13   ` [PATCH 4/7] gpio: acpi: Fixup kerneldoc Andy Shevchenko
2017-07-25  8:50     ` Mika Westerberg
2017-08-02 12:09   ` Linus Walleij
2017-07-24 14:57 ` [PATCH 5/7] gpio: sysfs: " Thierry Reding
2017-08-02 12:10   ` Linus Walleij
2017-07-24 14:57 ` [PATCH 6/7] docs: driver-api: Add GPIO section Thierry Reding
2017-08-02 12:13   ` Linus Walleij
2017-07-24 14:57 ` [PATCH 7/7] gpio: Use unsigned int for of_gpio_n_cells Thierry Reding
2017-08-02 12:14   ` Linus Walleij
2017-07-31 11:02 ` [PATCH 1/7] gpio: Cleanup kerneldoc Thierry Reding
2017-08-02 12:04   ` Linus Walleij
2017-08-02 12:06 ` Linus Walleij

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=20170724145728.7662-4-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).