linux-kernel - [PATCH] firmware: arm_scmi: fix typos in comments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 21 May 2022 13:10:58 +0200
From:   Julia Lawall <Julia.Lawall@...ia.fr>
To:     Sudeep Holla <sudeep.holla@....com>
Cc:     kernel-janitors@...r.kernel.org,
        Cristian Marussi <cristian.marussi@....com>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [PATCH] firmware: arm_scmi: fix typos in comments

Spelling mistakes (triple letters) in comments.
Detected with the help of Coccinelle.

Signed-off-by: Julia Lawall <Julia.Lawall@...ia.fr>

---
 drivers/firmware/arm_scmi/driver.c |    2 +-
 drivers/firmware/arm_scmi/smc.c    |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/firmware/arm_scmi/driver.c b/drivers/firmware/arm_scmi/driver.c
index c1922bd650ae..3846b46eb8f7 100644
--- a/drivers/firmware/arm_scmi/driver.c
+++ b/drivers/firmware/arm_scmi/driver.c
@@ -1117,7 +1117,7 @@ struct scmi_msg_resp_domain_name_get {
  *	  stored as a NULL terminated string.
  * @len: The len in bytes of the @name char array.
  *
- * Return: 0 on Succcess
+ * Return: 0 on Success
  */
 static int scmi_common_extended_name_get(const struct scmi_protocol_handle *ph,
 					 u8 cmd_id, u32 res_id, char *name,
diff --git a/drivers/firmware/arm_scmi/smc.c b/drivers/firmware/arm_scmi/smc.c
index 745acfdd0b3d..13d59a1d7844 100644
--- a/drivers/firmware/arm_scmi/smc.c
+++ b/drivers/firmware/arm_scmi/smc.c
@@ -236,7 +236,7 @@ const struct scmi_desc scmi_smc_desc = {
 	 * once the SMC instruction has completed successfully, the issued
 	 * SCMI command would have been already fully processed by the SCMI
 	 * platform firmware and so any possible response value expected
-	 * for the issued command will be immmediately ready to be fetched
+	 * for the issued command will be immediately ready to be fetched
 	 * from the shared memory area.
 	 */
 	.sync_cmds_completed_on_ret = true,