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 5/7] gpio: sysfs: Fixup kerneldoc
Date: Mon, 24 Jul 2017 16:57:26 +0200 [thread overview]
Message-ID: <20170724145728.7662-5-thierry.reding@gmail.com> (raw)
In-Reply-To: <20170724145728.7662-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Fix up some references to parameters to match the code.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
drivers/gpio/gpiolib-sysfs.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpio/gpiolib-sysfs.c b/drivers/gpio/gpiolib-sysfs.c
index 16fe9742597b..45b8c0679fee 100644
--- a/drivers/gpio/gpiolib-sysfs.c
+++ b/drivers/gpio/gpiolib-sysfs.c
@@ -534,8 +534,8 @@ static struct class gpio_class = {
/**
* gpiod_export - export a GPIO through sysfs
- * @gpio: gpio to make available, already requested
- * @direction_may_change: true if userspace may change gpio direction
+ * @desc: GPIO to make available, already requested
+ * @direction_may_change: true if userspace may change GPIO direction
* Context: arch_initcall or later
*
* When drivers want to make a GPIO accessible to userspace after they
@@ -643,7 +643,7 @@ static int match_export(struct device *dev, const void *desc)
* gpiod_export_link - create a sysfs link to an exported GPIO node
* @dev: device under which to create symlink
* @name: name of the symlink
- * @gpio: gpio to create symlink to, already exported
+ * @desc: GPIO to create symlink to, already exported
*
* Set up a symlink from /sys/.../dev/name to /sys/class/gpio/gpioN
* node. Caller is responsible for unlinking.
@@ -674,7 +674,7 @@ EXPORT_SYMBOL_GPL(gpiod_export_link);
/**
* gpiod_unexport - reverse effect of gpiod_export()
- * @gpio: gpio to make unavailable
+ * @desc: GPIO to make unavailable
*
* This is implicit on gpiod_free().
*/
--
2.13.3
next prev 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 ` [PATCH 4/7] gpio: acpi: Fixup kerneldoc Thierry Reding
2017-07-24 15:13 ` Andy Shevchenko
2017-07-25 8:50 ` Mika Westerberg
2017-08-02 12:09 ` Linus Walleij
2017-07-24 14:57 ` Thierry Reding [this message]
2017-08-02 12:10 ` [PATCH 5/7] gpio: sysfs: " 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-5-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).