From: Andreas Larsson <andreas@gaisler.com>
To: "Thorsten Blum" <thorsten.blum@linux.dev>,
"David S. Miller" <davem@davemloft.net>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-hardening@vger.kernel.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] sparc: PCI: Replace deprecated strcpy with strscpy
Date: Fri, 26 Sep 2025 16:44:09 +0200 [thread overview]
Message-ID: <bdef00f9-4e66-4984-9b39-85b485bdc2cb@gaisler.com> (raw)
In-Reply-To: <20250922210408.1723452-1-thorsten.blum@linux.dev>
On 2025-09-22 23:03, Thorsten Blum wrote:
> strcpy() is deprecated; use strscpy() instead.
>
> No functional changes intended.
>
> Link: https://github.com/KSPP/linux/issues/88
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
For the series:
Reviewed-by: Andreas Larsson <andreas@gaisler.com>
Picking this up to my for-next.
Thanks,
Andreas
next prev parent reply other threads:[~2025-09-26 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 21:03 [PATCH 1/8] sparc: PCI: Replace deprecated strcpy with strscpy Thorsten Blum
2025-09-22 21:03 ` [PATCH 2/8] sparc: parport: Replace deprecated strcpy with strscpy in ecpp_probe Thorsten Blum
2025-09-22 21:03 ` [PATCH 3/8] sparc: floppy: Replace deprecated strcpy with strscpy in sun_floppy_init Thorsten Blum
2025-10-13 20:57 ` Andy Shevchenko
2025-09-22 21:03 ` [PATCH 4/8] sparc: Replace deprecated strcpy with strscpy in prom_nextprop Thorsten Blum
2025-09-22 21:03 ` [PATCH 5/8] sparc: Replace deprecated strcpy with strscpy Thorsten Blum
2025-09-22 21:03 ` [PATCH 6/8] sparc32: " Thorsten Blum
2025-09-22 21:03 ` [PATCH 7/8] sparc64: Replace deprecated strcpy with strscpy in build_path_component Thorsten Blum
2025-09-22 21:03 ` [PATCH 8/8] sparc: Replace deprecated strcpy with strscpy in handle_nextprop_quirks Thorsten Blum
2025-09-26 14:44 ` Andreas Larsson [this message]
2025-09-26 15:32 ` [PATCH 1/8] sparc: PCI: Replace deprecated strcpy with strscpy Andreas Larsson
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=bdef00f9-4e66-4984-9b39-85b485bdc2cb@gaisler.com \
--to=andreas@gaisler.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
/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