From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomasz Unger <tomasz.unger@yahoo.pl>
Cc: 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] staging: greybus: use sysfs_emit instead of sprintf in gbphy.c
Date: Tue, 1 Sep 2026 12:05:48 +0200 [thread overview]
Message-ID: <2026090135-subplot-robbing-8da8@gregkh> (raw)
In-Reply-To: <20260818-greybus-gbphy-sysfs-emit-v1-1-cfc81322e727@yahoo.pl>
On Tue, Aug 18, 2026 at 07:35:54PM +0200, Tomasz Unger wrote:
> Per Documentation/filesystems/sysfs.rst, new implementations of
> show() methods should only use sysfs_emit() or sysfs_emit_at()
> when formatting the value to be returned to user space, since it
> is aware of the sysfs PAGE_SIZE buffer and includes sanity checks
> that sprintf() lacks.
>
> Signed-off-by: Tomasz Unger <tomasz.unger@yahoo.pl>
> ---
> Verified with checkpatch.pl - no errors or warnings.
> Compiled the gb-gbphy module successfully with CONFIG_GREYBUS=m
> and CONFIG_GREYBUS_BRIDGED_PHY=m (both previously disabled).
> Both greybus.ko and gb-gbphy.ko load without errors in a QEMU
> environment (verified via insmod and lsmod). This confirms the
> modules load cleanly but does not exercise the changed sysfs
> show() code path, which would require an actual Greybus device
> (or a userspace simulator such as gbsim) bound to the driver.
> ---
> drivers/staging/greybus/gbphy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/greybus/gbphy.c b/drivers/staging/greybus/gbphy.c
> index bdb0f5164a6f..bb9a5b538e6e 100644
> --- a/drivers/staging/greybus/gbphy.c
> +++ b/drivers/staging/greybus/gbphy.c
> @@ -31,7 +31,7 @@ static ssize_t protocol_id_show(struct device *dev,
> {
> struct gbphy_device *gbphy_dev = to_gbphy_dev(dev);
>
> - return sprintf(buf, "0x%02x\n", gbphy_dev->cport_desc->protocol_id);
> + return sysfs_emit(buf, "0x%02x\n", gbphy_dev->cport_desc->protocol_id);
> }
> static DEVICE_ATTR_RO(protocol_id);
>
>
> ---
> base-commit: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f
> change-id: 20260818-greybus-gbphy-sysfs-emit-69739912458e
>
> Best regards,
> --
> Tomasz Unger <tomasz.unger@yahoo.pl>
>
>
Please see the archives for why this patch has been rejected in the
past.
thanks,
greg k-h
prev parent reply other threads:[~2026-09-01 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260818-greybus-gbphy-sysfs-emit-v1-1-cfc81322e727.ref@yahoo.pl>
2026-08-18 17:35 ` Tomasz Unger
2026-09-01 10:05 ` Greg Kroah-Hartman [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=2026090135-subplot-robbing-8da8@gregkh \
--to=gregkh@linuxfoundation.org \
--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=tomasz.unger@yahoo.pl \
/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®