Skip to contentSkip to conversation

fsi: Replace snprintf in show functions with sysfs_emit

PATCH In review [email protected] 2 participants 2 messages Jul 13, 2023 – Jul 17, 2023 1 message not in the archive FSI

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

PATCH 1/1 fsi: Replace snprintf in show functions with sysfs_emit

Fix the following coccicheck warning:
drivers/macintosh/ams/ams-core.c:53: WARNING: use scnprintf or
sprintf.

./drivers/fsi/fsi-master-gpio.c:721:8-16: WARNING: use scnprintf or sprintf

---
 drivers/fsi/fsi-master-gpio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/fsi/fsi-master-gpio.c +1 -1
index 7d5f29b4b595..75499365729f 100644
@@ -718,7 +718,7 @@ static ssize_t external_mode_show(struct device *dev,
 {
     struct fsi_master_gpio *master = dev_get_drvdata(dev);
 
-    return snprintf(buf, PAGE_SIZE - 1, "%u\n",
+    return scnprintf(buf, PAGE_SIZE - 1, "%u\n",
             master->external_mode ? 1 : 0);
 }
#2 lore raw
Quoted 15 lines · On Thu, Jul 13, 2023 at 05:29:21PM +0800, [email protected] wrote:

Fix the following coccicheck warning:
drivers/macintosh/ams/ams-core.c:53: WARNING: use scnprintf or sprintf.

./drivers/fsi/fsi-master-gpio.c:721:8-16: WARNING: use scnprintf or sprintf

---
 drivers/fsi/fsi-master-gpio.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/fsi/fsi-master-gpio.c +0 -0
index 7d5f29b4b595..75499365729f 100644

drivers/fsi/fsi-master-gpio.c static ssize_t external_mode_show(struct device *dev, · line 723

Quoted 7 lines
drivers/fsi/fsi-master-gpio.c +1 -1
@@ -718,7 +718,7 @@ static ssize_t external_mode_show(struct device *dev,
 {
     struct fsi_master_gpio *master = dev_get_drvdata(dev);
 
-    return snprintf(buf, PAGE_SIZE - 1, "%u\n",
+    return scnprintf(buf, PAGE_SIZE - 1, "%u\n",
             master->external_mode ? 1 : 0);
 }

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.

You are receiving this message because of the following common error(s) as indicated below:

- Your patch is malformed (tabs converted to spaces, linewrapped, etc.) and can not be applied. Please read the file, Documentation/process/email-clients.rst in order to fix this.

- You sent multiple patches, yet no indication of which ones should be applied in which order. Greg could just guess, but if you are receiving this email, he guessed wrong and the patches didn't apply. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for a description of how to do this so that Greg has a chance to apply these correctly.

- You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what is needed in order to properly describe the change.

- You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what a proper
Subject: line should look like.

- It looks like you did not use your "real" name for the patch on either the Signed-off-by: line, or the From: line (both of which have to match). Please read the kernel file, Documentation/process/submitting-patches.rst for how to do this correctly.

If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.

thanks,

greg k-h's patch email bot