public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Rahul Kumar <rk0006818@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org
Subject: Re: [PATCH] firmware: stratix10-rsu: replace scnprintf() with sysfs_emit() in *_show() functions
Date: Mon, 3 Nov 2025 22:45:05 -0600	[thread overview]
Message-ID: <26032cb1-53c6-46a1-b3eb-e1876142bf1c@kernel.org> (raw)
In-Reply-To: <CAKY2RybBidcyMtUY8mwyT=F2e5f=HT9HR6JXmgz+UyU6_S3kUQ@mail.gmail.com>



On 11/2/25 23:55, Rahul Kumar wrote:
> On Wed, Oct 15, 2025 at 3:11 PM Rahul Kumar <rk0006818@gmail.com> wrote:
>>
>> Replace scnprintf() with sysfs_emit() in sysfs *_show() functions
>> in stratix10-rsu.c to follow the kernel's guidelines from
>> Documentation/filesystems/sysfs.rst.
>>
>> This improves consistency, safety, and makes the code easier to
>> maintain and update in the future.
>>
>> Signed-off-by: Rahul Kumar <rk0006818@gmail.com>
>> ---
>>   drivers/firmware/stratix10-rsu.c | 7 +++----
>>   1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/firmware/stratix10-rsu.c b/drivers/firmware/stratix10-rsu.c
>> index 1ea39a0a76c7..53c896ceca9a 100644
>> --- a/drivers/firmware/stratix10-rsu.c
>> +++ b/drivers/firmware/stratix10-rsu.c
>> @@ -454,8 +454,7 @@ static ssize_t max_retry_show(struct device *dev,
>>          if (!priv)
>>                  return -ENODEV;
>>
>> -       return scnprintf(buf, sizeof(priv->max_retry),
>> -                        "0x%08x\n", priv->max_retry);
>> +       return sysfs_emit(buf, "0x%08x\n", priv->max_retry);
>>   }
>>
>>   static ssize_t dcmf0_show(struct device *dev,
>> @@ -632,7 +631,7 @@ static ssize_t spt0_address_show(struct device *dev,
>>          if (priv->spt0_address == INVALID_SPT_ADDRESS)
>>                  return -EIO;
>>
>> -       return scnprintf(buf, PAGE_SIZE, "0x%08lx\n", priv->spt0_address);
>> +       return sysfs_emit(buf, "0x%08lx\n", priv->spt0_address);
>>   }
>>
>>   static ssize_t spt1_address_show(struct device *dev,
>> @@ -646,7 +645,7 @@ static ssize_t spt1_address_show(struct device *dev,
>>          if (priv->spt1_address == INVALID_SPT_ADDRESS)
>>                  return -EIO;
>>
>> -       return scnprintf(buf, PAGE_SIZE, "0x%08lx\n", priv->spt1_address);
>> +       return sysfs_emit(buf, "0x%08lx\n", priv->spt1_address);
>>   }
>>
>>   static DEVICE_ATTR_RO(current_image);
>> --
>> 2.43.0
>>
> 
> Hi Dinguyen,
> 
> Just following up to see if you’ve had a chance to review this patch,
> or if there’s anything more needed from my side.
> 
> Link to v1:
> https://lore.kernel.org/all/20251015094117.535157-1-rk0006818@gmail.com/
> 
> Thanks,
> Rahul

Sorry about that. I've applied it.

Thanks,
Dinh


  reply	other threads:[~2025-11-04  4:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15  9:41 [PATCH] firmware: stratix10-rsu: replace scnprintf() with sysfs_emit() in *_show() functions Rahul Kumar
2025-11-03  5:55 ` Rahul Kumar
2025-11-04  4:45   ` Dinh Nguyen [this message]
2025-11-11  6:38     ` Rahul Kumar
2025-11-11 11:42       ` Dinh Nguyen

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=26032cb1-53c6-46a1-b3eb-e1876142bf1c@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rk0006818@gmail.com \
    --cc=skhan@linuxfoundation.org \
    /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