From: Dan Carpenter <dan.carpenter@linaro.org>
To: Neel Bullywon <neelb2403@gmail.com>
Cc: Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: greybus: gbphy: replace sprintf() with sysfs_emit()
Date: Wed, 4 Feb 2026 13:41:08 +0300 [thread overview]
Message-ID: <aYMiRAuE_GxwQMWt@stanley.mountain> (raw)
In-Reply-To: <20260204101342.71267-1-neelb2403@gmail.com>
It's best to wait a day between resends.
On Wed, Feb 04, 2026 at 05:13:42AM -0500, Neel Bullywon wrote:
> Replaced sprintf() with sysfs_emit() in the protocol_id_show() sysfs
I really hate to comment on this, because I famously get annoyed by
people who act like it's soooo important and we have one "reviewer" who
wants every sentence to be in imperative tense. But past tense is kind
of ugly. You did it right in the Subject on v2. Use "Replace" instead
of "Replaced" here as well.
Btw, if someone provides you a commit message, then they're basically
obligated to allow it.
> attribute function. This code is safe, as replacing sprintf() with
s/as/as-is/?
> sysfs_emit() gets rid of calls to sprintf()
The line break is weird.
> as part of kernel hardening and sysfs_emit() is more appropriate in
> this context.
>
> Signed-off-by: Neel Bullywon <neelb2403@gmail.com>
> ---
> This was compile-tested only (no VM/hardware used)
> ---
You need to put a little note here to say what changed.
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
regards,
dan carpenter
next prev parent reply other threads:[~2026-02-04 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 10:13 [PATCH v2] staging: greybus: gbphy: replace sprintf() with sysfs_emit() Neel Bullywon
2026-02-04 10:41 ` Dan Carpenter [this message]
2026-02-04 12:11 ` Greg Kroah-Hartman
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=aYMiRAuE_GxwQMWt@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=neelb2403@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