From: Bartosz Golaszewski <brgl@bgdev.pl>
To: David Lechner <dlechner@baylibre.com>
Cc: Kent Gibson <warthog618@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: gpio: fix typo
Date: Tue, 2 Apr 2024 10:50:42 +0200 [thread overview]
Message-ID: <CAMRc=MfUQ5+Tq3M8=gABA_t+bumWs8=5RZ8gVJXxFLg0cvcMpA@mail.gmail.com> (raw)
In-Reply-To: <20240329144318.376939-1-dlechner@baylibre.com>
On Fri, Mar 29, 2024 at 3:43 PM David Lechner <dlechner@baylibre.com> wrote:
>
> EOPNOTSUPP has two 'P's.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
> Documentation/userspace-api/gpio/gpio-v2-get-line-ioctl.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/userspace-api/gpio/gpio-v2-get-line-ioctl.rst b/Documentation/userspace-api/gpio/gpio-v2-get-line-ioctl.rst
> index 56b975801b6a..6615d6ced755 100644
> --- a/Documentation/userspace-api/gpio/gpio-v2-get-line-ioctl.rst
> +++ b/Documentation/userspace-api/gpio/gpio-v2-get-line-ioctl.rst
> @@ -81,7 +81,7 @@ Only one event clock flag, ``GPIO_V2_LINE_FLAG_EVENT_CLOCK_xxx``, may be set.
> If none are set then the event clock defaults to ``CLOCK_MONOTONIC``.
> The ``GPIO_V2_LINE_FLAG_EVENT_CLOCK_HTE`` flag requires supporting hardware
> and a kernel with ``CONFIG_HTE`` set. Requesting HTE from a device that
> -doesn't support it is an error (**EOPNOTSUP**).
> +doesn't support it is an error (**EOPNOTSUPP**).
>
> The :c:type:`debounce_period_us<gpio_v2_line_attribute>` attribute may only
> be applied to lines with ``GPIO_V2_LINE_FLAG_INPUT`` set. When set, debounce
> --
> 2.43.2
>
Applied, thanks!
Bart
next prev parent reply other threads:[~2024-04-02 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 14:43 [PATCH] Documentation: gpio: fix typo David Lechner
2024-04-02 8:50 ` Bartosz Golaszewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-14 15:54 [PATCH] Documentation: gpio: Fix typo Wolfram Sang
2021-01-18 9:02 ` Wolfram Sang
2021-01-22 9:44 ` 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='CAMRc=MfUQ5+Tq3M8=gABA_t+bumWs8=5RZ8gVJXxFLg0cvcMpA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.