[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <596CAA63-C3F8-4C90-B898-259B7CF8AD6D@linux.dev>
Date: Fri, 26 Sep 2025 00:35:07 +0200
From: Thorsten Blum <thorsten.blum@...ux.dev>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>
Cc: dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org,
Alex Deucher <alexander.deucher@....com>
Subject: Re: [PATCH RESEND] drm: Use strscpy() instead of strscpy_pad()
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@...ux.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
Powered by blists - more mailing lists