mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs: make sysfs_emit() return ssize_t
Date: Thu, 7 Mar 2024 22:04:41 +0000	[thread overview]
Message-ID: <2024030713-favorably-liking-2135@gregkh> (raw)
In-Reply-To: <33cd8f96-4b4f-4741-ac05-ef1bd267ce6b@p183>

On Mon, Feb 05, 2024 at 01:11:36PM +0300, Alexey Dobriyan wrote:
> sysfs_emit() is most often found in functions returning ssize_t
> not int:
> 
> 	static ssize_t oops_count_show(...)
> 	{
> 		return sysfs_emit(page, ...);
> 	}
> 
> This pattern results in sign-extension instruction between
> sysfs_emit() return value (int) and caller return value (which is
> ssize_t).

Is that a problem?

> But it is better to do sign-extension once inside sysfs_emit()
> then duplicate it at nearly every call site on 64-bit.

Why is that better?  Does this affect code generation?  If so, how much?
And to what affect?

And the function itself really is dealing with an int, it's up to the
caller to want to do something with that, not the sysfs_emit() call
itself.

thanks,

greg k-h

  reply	other threads:[~2024-03-07 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 10:11 Alexey Dobriyan
2024-03-07 22:04 ` Greg Kroah-Hartman [this message]
2024-03-08  6:26   ` Alexey Dobriyan
2024-03-08  9:01     ` Greg Kroah-Hartman
2024-03-10 19:21     ` David Laight
2024-03-11  4:55       ` Alexey Dobriyan

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=2024030713-favorably-liking-2135@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    /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®