From: Jarkko Sakkinen <jarkko@kernel.org>
To: WangYuli <wangyuli@uniontech.com>
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org,
James.Bottomley@hansenpartnership.com, stefanb@linux.ibm.com,
ardb@kernel.org, roberto.sassu@huawei.com,
viro@zeniv.linux.org.uk, gourry@gourry.net
Subject: Re: [PATCH] MAINTAINERS: Add include/linux/tpm*.h to TPM maintainers
Date: Fri, 14 Mar 2025 17:05:50 +0200 [thread overview]
Message-ID: <Z9RFzkzAn1Vi76hY@kernel.org> (raw)
In-Reply-To: <F0B8DC7D8609F78E+f602292f-27ed-41e0-81d9-911174ee1da0@uniontech.com>
On Wed, Mar 12, 2025 at 02:48:51PM +0800, WangYuli wrote:
> Hi Jarkko,
>
> On 2025/3/12 14:23, Jarkko Sakkinen wrote:
> > "Subnames" are separated with space, not with camel case.
> >
> It's just a matter of regional cultural differences.
>
> In my country, we don't have the concept of "Subname" in names.
>
> We only have "Surname" and "Given name", and our convention is to put the
> surname first, followed by the given name, without a space in between.
>
> So I don't think I need to make any changes to my sign-off.
OK, I don't really mind the order, and I did not about the white space
part.
So with that
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
>
> Of course, as you are the TPM maintainer, I respect your opinion, and if you
> strongly insist, I can change my sign-off but only for all future
> TPM-related commits, perhaps by using Unicode characters instead of spelling
> it out with English letters.
It's always good to get educated, no worries.
>
> Thanks,
>
> --
>
> 王昱力
>
BR, Jarkko
prev parent reply other threads:[~2025-03-14 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:14 [PATCH] MAINTAINERS: Add include/linux/tpm*.h to TPM maintainers WangYuli
2025-03-12 6:23 ` Jarkko Sakkinen
2025-03-12 6:48 ` WangYuli
2025-03-14 15:05 ` Jarkko Sakkinen [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=Z9RFzkzAn1Vi76hY@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ardb@kernel.org \
--cc=gourry@gourry.net \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=roberto.sassu@huawei.com \
--cc=stefanb@linux.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wangyuli@uniontech.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