From: Greg KH <gregkh@linuxfoundation.org>
To: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
Cc: alexander.usyskin@intel.com, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mei: bus: Add newline to sysfs attribute outputs
Date: Mon, 3 Nov 2025 09:25:52 +0900 [thread overview]
Message-ID: <2025110319-activist-register-d119@gregkh> (raw)
In-Reply-To: <83d8d2bb-767a-4dd6-8e1b-de96164cad4c@oss.qualcomm.com>
On Thu, Oct 30, 2025 at 09:11:34PM +0800, Zhongqiu Han wrote:
> On 10/30/2025 8:32 PM, Greg KH wrote:
> > On Thu, Oct 30, 2025 at 08:30:00PM +0800, Zhongqiu Han wrote:
> > > Append newline characters to sysfs_emit() outputs in func max_conn_show(),
> > > fixed_show(), and vtag_show(). This aligns with common kernel conventions
> > > and improves readability for userspace tools that expect
> > > newline-terminated values.
> >
> > What userspace tool reads these values today? Will this user/kernel api
> > break them? How was this tested?
> >
> > thanks,
> >
> > greg k-h
>
> Hi Greg,
> Thanks for your review~
>
> Apologies for the confusion in the commit message — there isn't
> actually a userspace tool that depends on the newline in this case. I
> just made the change to follow common sysfs formatting practices and
> improve consistency.
That's fine, but please work with the people that wrote the tools that
depend on these files today to verify it will not break anything, and
then resubmit the patch with that information in the changelog.
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-03 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 12:30 [PATCH] mei: bus: Add newline to sysfs attribute outputs Zhongqiu Han
2025-10-30 12:32 ` Greg KH
2025-10-30 13:11 ` Zhongqiu Han
2025-11-03 0:25 ` Greg KH [this message]
2025-11-03 13:43 ` Zhongqiu Han
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=2025110319-activist-register-d119@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongqiu.han@oss.qualcomm.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