From: Kent Gibson <warthog618@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] gpiolib: cdev: Fix typo in kernel doc for struct line
Date: Fri, 21 Oct 2022 20:53:36 +0800 [thread overview]
Message-ID: <Y1KWULsdyTvmuN/k@sol> (raw)
In-Reply-To: <20221020153914.63260-1-andriy.shevchenko@linux.intel.com>
On Thu, Oct 20, 2022 at 06:39:14PM +0300, Andy Shevchenko wrote:
> When eflags has been renamed to the edflags, the kernel doc change were
> missed. Update kernel doc accordingly.
>
> Fixes: b1a92e94560d ("gpiolib: cdev: consolidate edge detector configuration flags")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Kent Gibson <warthog618@gmail.com>
> ---
> drivers/gpio/gpiolib-cdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpiolib-cdev.c b/drivers/gpio/gpiolib-cdev.c
> index 0c84b011a64a..f9288e41e3a7 100644
> --- a/drivers/gpio/gpiolib-cdev.c
> +++ b/drivers/gpio/gpiolib-cdev.c
> @@ -412,7 +412,7 @@ static int linehandle_create(struct gpio_device *gdev, void __user *ip)
> * @desc: the GPIO descriptor for this line.
> * @req: the corresponding line request
> * @irq: the interrupt triggered in response to events on this GPIO
> - * @eflags: the edge flags, GPIO_V2_LINE_FLAG_EDGE_RISING and/or
> + * @edflags: the edge flags, GPIO_V2_LINE_FLAG_EDGE_RISING and/or
> * GPIO_V2_LINE_FLAG_EDGE_FALLING, indicating the edge detection applied
> * @timestamp_ns: cache for the timestamp storing it between hardirq and
> * IRQ thread, used to bring the timestamp close to the actual event
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-10-21 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:39 [PATCH v1 1/1] gpiolib: cdev: Fix typo in kernel doc for struct line Andy Shevchenko
2022-10-21 12:53 ` Kent Gibson [this message]
2022-10-25 16:48 ` Andy Shevchenko
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=Y1KWULsdyTvmuN/k@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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