From: Thorsten Blum <thorsten.blum@linux.dev>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH RESEND] drm: Use strscpy() instead of strscpy_pad()
Date: Fri, 26 Sep 2025 00:35:07 +0200 [thread overview]
Message-ID: <596CAA63-C3F8-4C90-B898-259B7CF8AD6D@linux.dev> (raw)
In-Reply-To: <20250908102217.3725-1-thorsten.blum@linux.dev>
Hi all,
> On 8. Sep 2025, Thorsten Blum wrote:
>
> kzalloc() already zero-initializes the destination buffers, making
> strscpy() sufficient for safely copying the names. The additional
> NUL-padding performed by strscpy_pad() is unnecessary.
>
> If the destination buffer has a fixed length, strscpy() automatically
> determines its size using sizeof() when the argument is omitted. This
> makes the explicit size arguments unnecessary.
>
> No functional changes intended.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
I've been resending this patch since April and I'm wondering what else I
could do to get this reviewed and/or merged?
The patch still applies to both linux-next and master.
Thanks,
Thorsten
next prev parent reply other threads:[~2025-09-25 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 10:22 [PATCH RESEND] drm: Use strscpy() instead of strscpy_pad() Thorsten Blum
2025-09-25 22:35 ` Thorsten Blum [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-17 23:19 Thorsten Blum
2025-07-16 21:14 Thorsten Blum
2025-06-19 14:51 Thorsten Blum
2025-05-21 23:18 Thorsten Blum
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=596CAA63-C3F8-4C90-B898-259B7CF8AD6D@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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.