From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atkbd - simplify atkbd_show_force_release()
Date: Sat, 24 Apr 2021 19:27:30 -0700 [thread overview]
Message-ID: <YITTkui8qer2S+4R@google.com> (raw)
In-Reply-To: <20210421201639.1541945-1-linux@rasmusvillemoes.dk>
Hi Rasmus,
On Wed, Apr 21, 2021 at 10:16:39PM +0200, Rasmus Villemoes wrote:
> We can just include the newline in the format string, and scnprintf()
> guarantees nul-termination. These days, sysfs_emit() is
> preferred in sysfs ->show methods, so switch to that.
Technically speaking the conversion is not 100% equivalent - original
code ensured that there is always a newline in the output. I kind of
like this, so maybe we need sysfs_emit_nl() or similar?
>
> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> ---
> drivers/input/keyboard/atkbd.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> index edc613efc158..b146a3ec631a 100644
> --- a/drivers/input/keyboard/atkbd.c
> +++ b/drivers/input/keyboard/atkbd.c
> @@ -1492,13 +1492,8 @@ static ssize_t atkbd_set_extra(struct atkbd *atkbd, const char *buf, size_t coun
>
> static ssize_t atkbd_show_force_release(struct atkbd *atkbd, char *buf)
> {
> - size_t len = scnprintf(buf, PAGE_SIZE - 1, "%*pbl",
> - ATKBD_KEYMAP_SIZE, atkbd->force_release_mask);
> -
> - buf[len++] = '\n';
> - buf[len] = '\0';
> -
> - return len;
> + return sysfs_emit(buf, "%*pbl\n",
> + ATKBD_KEYMAP_SIZE, atkbd->force_release_mask);
> }
>
> static ssize_t atkbd_set_force_release(struct atkbd *atkbd,
> --
> 2.29.2
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2021-04-25 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 20:16 [PATCH] Input: atkbd - simplify atkbd_show_force_release() Rasmus Villemoes
2021-04-25 2:27 ` Dmitry Torokhov [this message]
2021-04-26 7:06 ` Rasmus Villemoes
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=YITTkui8qer2S+4R@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.