From: Heiko Carstens <hca@linux.ibm.com>
To: yang.yang29@zte.com.cn
Cc: freude@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
xu.panda@zte.com.cn
Subject: Re: [PATCH linux-next v2] s390/zcrypt: use strscpy() to instead of strncpy()
Date: Tue, 3 Jan 2023 10:51:21 +0100 [thread overview]
Message-ID: <Y7P6mSuYkmP8g8Ot@osiris> (raw)
In-Reply-To: <202301031002076571212@zte.com.cn>
On Tue, Jan 03, 2023 at 10:02:07AM +0800, yang.yang29@zte.com.cn wrote:
> From: Yang Yang <yang.yang29@zte.com>
>
> The implementation of strscpy() is more robust and safer.
> That's now the recommended way to copy NUL-terminated strings.
>
> Signed-off-by: Yang Yang <yang.yang29@zte.com>
> Signed-off-by: Xu Panda <xu.panda@zte.com.cn>
> ---
> chang for v2
> - match the FROM with the Email
You sent this from yang.yang29@zte.com.cn, but the sign-off is without the
".cn" suffix. Can you please make sure that your sign-off chain actually
follows the rules as outlined in Documentation/process/submitting-patches.rst?
If you read that then the sign-off line from Xu Panda shouldn't be there,
since the patch was not authored or routed via Xu Panda.
next prev parent reply other threads:[~2023-01-03 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 2:02 [PATCH linux-next v2] s390/zcrypt: use strscpy() to instead of strncpy() yang.yang29
2023-01-03 9:51 ` Heiko Carstens [this message]
2023-01-05 14:01 ` Bagas Sanjaya
2023-01-10 3:16 ` yang.yang29
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=Y7P6mSuYkmP8g8Ot@osiris \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=xu.panda@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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