From: Greg KH <gregkh@linuxfoundation.org>
To: zntsproj <vacacax16@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, greybus-dev@lists.linaro.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
zntsproj <vseokaktusah7@gmail.com>
Subject: Re: [PATCH v4] Fix tiny typo in firmware-management docs
Date: Sun, 2 Nov 2025 20:41:08 +0900 [thread overview]
Message-ID: <2025110254-identical-tactful-a48a@gregkh> (raw)
In-Reply-To: <20251102113938.3116-1-vseokaktusah7@gmail.com>
On Sun, Nov 02, 2025 at 02:39:38PM +0300, zntsproj wrote:
> Signed-off-by: zntsproj <vseokaktusah7@gmail.com>
> ---
> .../staging/greybus/Documentation/firmware/firmware-management | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/greybus/Documentation/firmware/firmware-management b/drivers/staging/greybus/Documentation/firmware/firmware-management
> index 7918257e5..393455557 100644
> --- a/drivers/staging/greybus/Documentation/firmware/firmware-management
> +++ b/drivers/staging/greybus/Documentation/firmware/firmware-management
> @@ -193,7 +193,7 @@ Identifying the Character Device
>
> There can be multiple devices present in /dev/ directory with name
> gb-authenticate-N and user first needs to identify the character device used for
> -authentication a of particular interface.
> +authentication of a particular interface.
>
> The Authentication core creates a device of class 'gb_authenticate', which shall
> be used by the user to identify the right character device for it. The class
> --
> 2.51.2
>
>
Why did you ignore my bot's recommendations?
prev parent reply other threads:[~2025-11-02 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 11:39 [PATCH v4] Fix tiny typo in firmware-management docs zntsproj
2025-11-02 11:41 ` Greg KH [this message]
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=2025110254-identical-tactful-a48a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=vacacax16@gmail.com \
--cc=vseokaktusah7@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 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).