[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20251101074616.11211-1-vseokaktusah7@gmail.com>
Date: Sat, 1 Nov 2025 10:46:16 +0300
From: zntsproj <vacacax16@...il.com>
To: linux-kernel@...r.kernel.org
Cc: greybus-dev@...ts.linaro.org,
zntsproj <vseokaktusah7@...il.com>
Subject: [PATCH] Fix tiny typo in firmware-management docs
Signed-off-by: zntsproj <vseokaktusah7@...il.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
Powered by blists - more mailing lists