From: Krzysztof Kozlowski <krzk@kernel.org>
To: tomasz.unger@yahoo.pl
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] NFC: s3fwrn5: Replace strcpy() with strscpy()
Date: Mon, 2 Mar 2026 10:06:49 +0100 [thread overview]
Message-ID: <e29a8f61-8a53-4a5a-864d-bd15f42f87e9@kernel.org> (raw)
In-Reply-To: <20260301174950.226192-1-tomasz.unger@yahoo.pl>
On 01/03/2026 18:49, tomasz.unger@yahoo.pl wrote:
> From: Tomasz Unger <tomasz.unger@yahoo.pl>
>
> Replace strcpy() with strscpy() which limits the copy to the size of
> the destination buffer. Since fw_info->fw_name is an array with a fixed, declared size, the
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
Best regards,
Krzysztof
prev parent reply other threads:[~2026-03-02 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260301174950.226192-1-tomasz.unger.ref@yahoo.pl>
2026-03-01 17:49 ` [PATCH net-next v2] NFC: s3fwrn5: Replace strcpy() with strscpy() tomasz.unger
2026-03-02 9:06 ` Krzysztof Kozlowski
2026-03-02 9:06 ` Krzysztof Kozlowski [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=e29a8f61-8a53-4a5a-864d-bd15f42f87e9@kernel.org \
--to=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tomasz.unger@yahoo.pl \
/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