From: Brian Cain <bcain@quicinc.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>
Subject: RE: [PATCH] hexagon: move from strlcpy with unused retval to strscpy
Date: Sat, 20 Aug 2022 17:43:21 +0000 [thread overview]
Message-ID: <BN7PR02MB4194E17163F8221AB873ECDEB86F9@BN7PR02MB4194.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20220818205938.6192-1-wsa+renesas@sang-engineering.com>
> -----Original Message-----
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
...
> Follow the advice of the below link and prefer 'strscpy' in this
> subsystem. Conversion is 1:1 because the return value is not used.
> Generated by a coccinelle script.
Acked-by: Brian Cain <bcain@quicinc.com>
prev parent reply other threads:[~2022-08-20 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 20:59 [PATCH] hexagon: move from strlcpy with unused retval to strscpy Wolfram Sang
2022-08-20 17:43 ` Brian Cain [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=BN7PR02MB4194E17163F8221AB873ECDEB86F9@BN7PR02MB4194.namprd02.prod.outlook.com \
--to=bcain@quicinc.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).