From: "Gary Chu(楚光庆)" <chuguangqing@inspur.com>
To: "Markus.Elfring@web.de" <Markus.Elfring@web.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"antonio@openvpn.net" <antonio@openvpn.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"sd@queasysnail.net" <sd@queasysnail.net>,
"horms@kernel.org" <horms@kernel.org>
Subject: Re: [PATCH v2 1/1] ovpn: use kmalloc_array() for array space allocation
Date: Wed, 3 Sep 2025 12:00:57 +0000 [thread overview]
Message-ID: <154e91e453c44817abbea33a7fb72e32@inspur.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
Hi Markus，
First of all, thank you for your reminder. According to your suggestion, the format "Chu Guangqing" should be used. However, in line with our company's signature conventions and my previous contributions to the kernel community, I have been using "chuguangqing". Therefore, I have to continue using this signature. The signature should not be changed frequently.
>
> > Signed-off-by: chuguangqing <chuguangqing@inspur.com>
>
> Would the personal name usually deviate a bit from the email identifier
> according to the Developer's Certificate of Origin?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docume
> ntation/process/submitting-patches.rst?h=v6.17-rc4#n436
>
> Regards,
> Markus
Best regards,
Chu Guangqing
<chuguangqing@inspur.com>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3931 bytes --]
next reply other threads:[~2025-09-03 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 12:00 Gary Chu(楚光庆) [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-01 11:21 [PATCH 1/1] ovpn: use kmalloc_array() for array space allocation chuguangqing
2025-09-02 9:00 ` PATCH v2 Re: " chuguangqing
2025-09-02 9:00 ` [PATCH v2 " chuguangqing
2025-09-02 13:15 ` Markus Elfring
2025-09-03 12:17 ` chuguangqing
2025-09-03 8:41 ` Antonio Quartulli
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=154e91e453c44817abbea33a7fb72e32@inspur.com \
--to=chuguangqing@inspur.com \
--cc=Markus.Elfring@web.de \
--cc=andrew+netdev@lunn.ch \
--cc=antonio@openvpn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.