public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	davidcomponentone@gmail.com, jejb@linux.ibm.com
Cc: martin.petersen@oracle.com, bvanassche@acm.org,
	yang.guang5@zte.com.cn, jiapeng.chong@linux.alibaba.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] scsi: csiostor: replace snprintf with sysfs_emit
Date: Tue, 08 Feb 2022 19:12:43 -0800	[thread overview]
Message-ID: <f4b63b5a4177e38dd80f102f87bbec3ea77d9fe8.camel@perches.com> (raw)
In-Reply-To: <148a5448-71f1-4f39-834b-eb9283de0bfb@opensource.wdc.com>

On Wed, 2022-02-09 at 11:36 +0900, Damien Le Moal wrote:
> On 2/9/22 09:40, davidcomponentone@gmail.com wrote:
> > From: Yang Guang <yang.guang5@zte.com.cn>
> > 
> > coccinelle report:
> > ./drivers/scsi/csiostor/csio_scsi.c:1433:8-16:
> > WARNING: use scnprintf or sprintf
> > ./drivers/scsi/csiostor/csio_scsi.c:1369:9-17:
> > WARNING: use scnprintf or sprintf
> > ./drivers/scsi/csiostor/csio_scsi.c:1479:8-16:
> > WARNING: use scnprintf or sprintf
> > 
> > Use sysfs_emit instead of scnprintf or sprintf makes more sense.
[]
> > diff --git a/drivers/scsi/csiostor/csio_scsi.c b/drivers/scsi/csiostor/csio_scsi.c
[]
> > @@ -1366,9 +1366,9 @@ csio_show_hw_state(struct device *dev,
> >  	struct csio_hw *hw = csio_lnode_to_hw(ln);
> >  
> >  	if (csio_is_hw_ready(hw))
> > -		return snprintf(buf, PAGE_SIZE, "ready\n");
> > +		return sysfs_emit(buf, "ready\n");
> >  	else
> > -		return snprintf(buf, PAGE_SIZE, "not ready\n");
> > +		return sysfs_emit(buf, "not ready\n");
> 
> While at it, you could remove the useless "else" above.

Or not.  It's fine as is.  It's just a style preference.

Another style option would be to use a ?: like any of

	return sysfs_emit(buf, "%sready\n", csio_is_hw_ready(hw) ? "" : "not ");
or
	return sysfs_emit(buf, "%s\n", csio_is_hw_ready(hw) ? "ready" : "not ready");
or
	return sysfs_emit(buf, csio_is_hw_ready(hw) ? "ready\n" : "not ready\n");



  reply	other threads:[~2022-02-09  3:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  0:40 [PATCH] scsi: csiostor: replace snprintf with sysfs_emit davidcomponentone
2022-02-09  2:36 ` Damien Le Moal
2022-02-09  3:12   ` Joe Perches [this message]
2022-02-09  3:16     ` Damien Le Moal
2022-02-09  3:34       ` Damien Le Moal

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=f4b63b5a4177e38dd80f102f87bbec3ea77d9fe8.camel@perches.com \
    --to=joe@perches.com \
    --cc=bvanassche@acm.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=davidcomponentone@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=yang.guang5@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