From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: Vaibhav Agarwal <vaibhav.sr@gmail.com>,
Mark Greer <mgreer@animalcreek.com>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: greybus: audio: Use sysfs_emit in show functions
Date: Tue, 24 Feb 2026 10:09:56 -0800 [thread overview]
Message-ID: <2026022438-gamma-blog-1561@gregkh> (raw)
In-Reply-To: <20260223181158.13234-1-chakrabortyshubham66@gmail.com>
On Mon, Feb 23, 2026 at 11:41:58PM +0530, Shubham Chakraborty wrote:
> Refactor sprintf to sysfs_emit in all show functions of the greybus
> audio manager module. This follows the standard kernel practice of
> using sysfs_emit for sysfs attributes, ensuring consistent output
> formatting and newline handling.
>
> Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
> ---
>
> v3:
> - Add patch history below the --- line as requested by Greg KH.
>
> v2:
> - Add missing Signed-off-by line.
> - Wrap commit message at 72 characters.
>
> drivers/staging/greybus/audio_manager_module.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/greybus/audio_manager_module.c b/drivers/staging/greybus/audio_manager_module.c
> index e87b82ca6..f22ee73eb 100644
> --- a/drivers/staging/greybus/audio_manager_module.c
> +++ b/drivers/staging/greybus/audio_manager_module.c
> @@ -76,7 +76,7 @@ static void gb_audio_module_release(struct kobject *kobj)
> static ssize_t gb_audio_module_name_show(struct gb_audio_manager_module *module,
> struct gb_audio_manager_module_attribute *attr, char *buf)
> {
> - return sprintf(buf, "%s", module->desc.name);
> + return sysfs_emit(buf, "%s\n", module->desc.name);
You just changed the output of all of these sysfs files by adding "\n"
to the end. Why?
I don't think that's wrong, BUT it is a user/kernel api change, so you
need to document it, and ideally, that would happen in a separate change
from this one.
So can you do the conversion to sysfs_emit() with NO change in the
output, and a second one to add the \n if you really think it is needed.
And is it needed? If so, why? What tool uses these files and does it
now still work?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-24 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 18:11 [PATCH v3] staging: greybus: audio: Use sysfs_emit in show functions Shubham Chakraborty
2026-02-24 18:09 ` Greg Kroah-Hartman [this message]
2026-02-24 19:05 ` Shubham Chakraborty
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=2026022438-gamma-blog-1561@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chakrabortyshubham66@gmail.com \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mgreer@animalcreek.com \
--cc=vaibhav.sr@gmail.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