From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ian Bridges <icb@fastmail.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - replace strlcat() with seq_buf and scnprintf()
Date: Sat, 11 Jul 2026 15:51:55 -0700 [thread overview]
Message-ID: <alLJCOD4fcYlnq7I@google.com> (raw)
In-Reply-To: <akyW4xkvCCROM0SE@dev>
On Tue, Jul 07, 2026 at 01:04:19AM -0500, Ian Bridges wrote:
> In preparation for removing the strlcat() API[1], replace its uses in
> i8042-acpipnpio.h.
>
> i8042_pnp_id_to_string() accumulates a variable number of PNP ids in
> a loop, which is what seq_buf is for. The kbd and aux probe functions
> build a name from at most three parts that are all known up front, so
> the whole construction becomes a single scnprintf() there.
>
> Link: https://github.com/KSPP/linux/issues/370 [1]
> Signed-off-by: Ian Bridges <icb@fastmail.org>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2026-07-11 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 6:04 [PATCH] Input: i8042 - replace strlcat() with seq_buf and scnprintf() Ian Bridges
2026-07-11 22:51 ` Dmitry Torokhov [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=alLJCOD4fcYlnq7I@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=icb@fastmail.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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