From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-doc@vger.kernel.org
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] Documentation: gpio: Fix typo
Date: Mon, 18 Jan 2021 10:02:02 +0100 [thread overview]
Message-ID: <20210118090202.GB1018@ninjato> (raw)
In-Reply-To: <20201214155440.2950-1-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On Mon, Dec 14, 2020 at 04:54:40PM +0100, Wolfram Sang wrote:
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
Does this go via doc or gpio?
> Documentation/driver-api/gpio/consumer.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/gpio/consumer.rst b/Documentation/driver-api/gpio/consumer.rst
> index 423492d125b9..86e7676c5f0d 100644
> --- a/Documentation/driver-api/gpio/consumer.rst
> +++ b/Documentation/driver-api/gpio/consumer.rst
> @@ -110,7 +110,7 @@ For a function using multiple GPIOs all of those can be obtained with one call::
>
> This function returns a struct gpio_descs which contains an array of
> descriptors. It also contains a pointer to a gpiolib private structure which,
> -if passed back to get/set array functions, may speed up I/O proocessing::
> +if passed back to get/set array functions, may speed up I/O processing::
>
> struct gpio_descs {
> struct gpio_array *info;
> --
> 2.28.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-18 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:54 [PATCH] Documentation: gpio: Fix typo Wolfram Sang
2021-01-18 9:02 ` Wolfram Sang [this message]
2021-01-22 9:44 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 14:43 [PATCH] Documentation: gpio: fix typo David Lechner
2024-04-02 8:50 ` Bartosz Golaszewski
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=20210118090202.GB1018@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).