Linux kernel staging patches
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Jose Nieto <jnieto.alaber@gmail.com>
Cc: Vaibhav Agarwal <vaibhav.sr@gmail.com>,
	Mark Greer <mgreer@animalcreek.com>,
	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] staging: greybus: audio: add missing newline to sysfs_emit()
Date: Thu, 29 Oct 2026 16:23:30 +0300	[thread overview]
Message-ID: <auNI0owLeK0gwOxF@stanley.mountain> (raw)
In-Reply-To: <20261029131122.167464-1-jnieto.alaber@gmail.com>

On Thu, Oct 29, 2026 at 02:11:22PM +0100, Jose Nieto wrote:
> The sysfs show() callbacks must emit a trailing newline. Commit 14c91651df34
> ("staging: greybus: audio: Use sysfs_emit in show functions") converted them
> to sysfs_emit() but dropped the newline. Restore it.

This would have been a convincing argument, but it's not true.

-       return sprintf(buf, "%s", module->desc.name);
+       return sysfs_emit(buf, "%s", module->desc.name);

There was never a newline and adding one now is a change to the user
space API.  We are allowed to change the API so long as it doesn't break
anything but no one has been able to check.

We have recieved this same patch over a dozen times now.  :P  It has
become a challenge to keep rejecting it over and over...  But I am a
stuborn person and the whole point of staging is to teach good habbits.

regards,
dan carpenter


      reply	other threads:[~2026-10-29 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 13:11 [PATCH] staging: greybus: audio: add missing newline to sysfs_emit() Jose Nieto
2026-10-29 13:23 ` Dan Carpenter [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=auNI0owLeK0gwOxF@stanley.mountain \
    --to=error27@gmail.com \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=jnieto.alaber@gmail.com \
    --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