From: John Garry <john.garry@huawei.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<guohanjun@huawei.com>
Subject: Re: [PATCH] [SCSI] libsas: add missing newline when printing 'enable' by sysfs
Date: Fri, 17 Jul 2020 08:54:19 +0100 [thread overview]
Message-ID: <648c18d0-cc0a-f444-e774-e0938f697e90@huawei.com> (raw)
In-Reply-To: <1594971374-40210-1-git-send-email-wangxiongfeng2@huawei.com>
On 17/07/2020 08:36, Xiongfeng Wang wrote:
Hi,
I think "scsi: scsi_transport_sas: " would be a better subject prefix,
as this is not libsas code.
> When I cat sysfs file 'enable' below 'sas_phy', it displays as follows.
> It's better to add a newline for easy reading.
>
> [root@localhost ~]# cat /sys/devices/pci0000:00/0000:00:0d.0/0000:0f:00.0/host3/phy-3:2/sas_phy/phy-3:2/enable
> 1[root@localhost ~]#
>
> Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Apart from above,
Reviewed-by: John Garry <john.garry@huawei.com>
> ---
> drivers/scsi/scsi_transport_sas.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/scsi_transport_sas.c b/drivers/scsi/scsi_transport_sas.c
> index 182fd25..e443dee 100644
> --- a/drivers/scsi/scsi_transport_sas.c
> +++ b/drivers/scsi/scsi_transport_sas.c
> @@ -563,7 +563,7 @@ static ssize_t do_sas_phy_enable(struct device *dev,
> {
> struct sas_phy *phy = transport_class_to_phy(dev);
>
> - return snprintf(buf, 20, "%d", phy->enabled);
> + return snprintf(buf, 20, "%d\n", phy->enabled);
> }
>
> static DEVICE_ATTR(enable, S_IRUGO | S_IWUSR, show_sas_phy_enable,
>
next prev parent reply other threads:[~2020-07-17 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 7:36 [PATCH] [SCSI] libsas: add missing newline when printing 'enable' by sysfs Xiongfeng Wang
2020-07-17 7:54 ` John Garry [this message]
2020-07-17 8:28 ` Xiongfeng Wang
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=648c18d0-cc0a-f444-e774-e0938f697e90@huawei.com \
--to=john.garry@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=wangxiongfeng2@huawei.com \
/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