From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: <xuwei5@hisilicon.com>, <linux-kernel@vger.kernel.org>,
<soc@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<liuyonglong@huawei.com>
Subject: Re: [PATCH] soc: hisilicon: kunpeng_hccs: Fix incorrect string assembly
Date: Fri, 14 Mar 2025 10:01:36 +0000 [thread overview]
Message-ID: <20250314100136.0000416f@huawei.com> (raw)
In-Reply-To: <20250314082856.3257783-1-lihuisong@huawei.com>
On Fri, 14 Mar 2025 16:28:56 +0800
Huisong Li <lihuisong@huawei.com> wrote:
> String assembly should use sysfs_emit_at() instead of sysfs_emit().
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
Fixes tag?
Otherwise looks good to me.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> drivers/soc/hisilicon/kunpeng_hccs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/hisilicon/kunpeng_hccs.c b/drivers/soc/hisilicon/kunpeng_hccs.c
> index 8aa8dec14911..444a8f59b7da 100644
> --- a/drivers/soc/hisilicon/kunpeng_hccs.c
> +++ b/drivers/soc/hisilicon/kunpeng_hccs.c
> @@ -1539,8 +1539,8 @@ static ssize_t used_types_show(struct kobject *kobj,
> u16 i;
>
> for (i = 0; i < hdev->used_type_num - 1; i++)
> - len += sysfs_emit(&buf[len], "%s ", hdev->type_name_maps[i].name);
> - len += sysfs_emit(&buf[len], "%s\n", hdev->type_name_maps[i].name);
> + len += sysfs_emit_at(buf, len, "%s ", hdev->type_name_maps[i].name);
> + len += sysfs_emit_at(buf, len, "%s\n", hdev->type_name_maps[i].name);
>
> return len;
> }
next prev parent reply other threads:[~2025-03-14 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 8:28 [PATCH] soc: hisilicon: kunpeng_hccs: Fix incorrect string assembly Huisong Li
2025-03-14 10:01 ` Jonathan Cameron [this message]
2025-03-14 10:08 ` lihuisong (C)
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=20250314100136.0000416f@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=soc@kernel.org \
--cc=xuwei5@hisilicon.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