From: Johan Hovold <johan@kernel.org>
To: cgel.zte@gmail.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
yao.jing2@zte.com.cn, zealci@zte.com.cn
Subject: Re: [PATCH v2] most: replace snprintf in show functions with sysfs_emit
Date: Mon, 8 Nov 2021 10:50:21 +0100 [thread overview]
Message-ID: <YYjy3QRXk/VL2Lze@hovoldconsulting.com> (raw)
In-Reply-To: <20211104114540.30622-1-yao.jing2@zte.com.cn>
On Thu, Nov 04, 2021 at 11:45:40AM +0000, cgel.zte@gmail.com wrote:
> From: Jing Yao <yao.jing2@zte.com.cn>
>
> coccicheck complains about the use of snprintf() in sysfs show
> functions:
> WARNING use scnprintf or sprintf
>
> Use sysfs_emit instead of scnprintf, snprintf or sprintf makes more
> sense.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Jing Yao <yao.jing2@zte.com.cn>
> ---
>
> Changes since v1:
> - Actually, the robot which is composed of lots of tools includes
> coccienlle.
> - Change the ignored snprintf().
> - Change the wrong Subject.
Ok, this is much better, but note that there are a lot more instances
like this in the "most" subsystem which this patch is not addressing so
the patch prefix should really have been:
"most: usb: ..."
since you're only handling the most usb driver.
> drivers/most/most_usb.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/most/most_usb.c b/drivers/most/most_usb.c
> index acabb7715b42..73258b24fea7 100644
> --- a/drivers/most/most_usb.c
> +++ b/drivers/most/most_usb.c
> @@ -831,7 +831,7 @@ static ssize_t value_show(struct device *dev, struct device_attribute *attr,
> int err;
>
> if (sysfs_streq(name, "arb_address"))
> - return snprintf(buf, PAGE_SIZE, "%04x\n", dci_obj->reg_addr);
> + return sysfs_emit(buf, "%04x\n", dci_obj->reg_addr);
>
> if (sysfs_streq(name, "arb_value"))
> reg_addr = dci_obj->reg_addr;
> @@ -843,7 +843,7 @@ static ssize_t value_show(struct device *dev, struct device_attribute *attr,
> if (err < 0)
> return err;
>
> - return snprintf(buf, PAGE_SIZE, "%04x\n", val);
> + return sysfs_emit(buf, "%04x\n", val);
> }
>
> static ssize_t value_store(struct device *dev, struct device_attribute *attr,
Other than that, looks good:
Reviewed-by: Johan Hovold <johan@kernel.org>
Johan
next prev parent reply other threads:[~2021-11-08 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 8:23 [PATCH] drivers: " cgel.zte
2021-11-03 8:27 ` Johan Hovold
2021-11-04 11:45 ` [PATCH v2] " cgel.zte
2021-11-08 9:50 ` Johan Hovold [this message]
2021-11-10 2:53 ` [PATCH v3] most: usb: " cgel.zte
2021-11-03 8:28 ` [PATCH] drivers: most: " Greg KH
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=YYjy3QRXk/VL2Lze@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=cgel.zte@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yao.jing2@zte.com.cn \
--cc=zealci@zte.com.cn \
/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
all inboxes | Powered by JetHome®