From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Joe Perches <joe@perches.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: Wed, 9 Feb 2022 12:34:24 +0900 [thread overview]
Message-ID: <8d7d36e6-66ac-a318-dfce-6d5b01b51f3c@opensource.wdc.com> (raw)
In-Reply-To: <0093948e-a408-61dd-3b51-524b6d112e35@opensource.wdc.com>
On 2022/02/09 12:16, Damien Le Moal wrote:
> On 2022/02/09 12:12, Joe Perches wrote:
>> 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.
>
> It is. I dislike the useless line of code in this case :)
>
>>
>> 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");
>
> That is nice and can make that
>
> return sysfs_emit(buf, "%sready\n", csio_is_hw_ready(hw) ? "" : "not ");
Oops. You did have that one listed... Read too quickly...
>
> too :)
>
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2022-02-09 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 0:40 davidcomponentone
2022-02-09 2:36 ` Damien Le Moal
2022-02-09 3:12 ` Joe Perches
2022-02-09 3:16 ` Damien Le Moal
2022-02-09 3:34 ` Damien Le Moal [this message]
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=8d7d36e6-66ac-a318-dfce-6d5b01b51f3c@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=bvanassche@acm.org \
--cc=davidcomponentone@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=joe@perches.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
all inboxes | Powered by JetHome®