From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: zhudi <zhudi21@huawei.com>,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
rose.chen@huawei.com, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH] rtnetlink: fix data overflow in rtnl_calcit()
Date: Fri, 16 Oct 2020 17:44:31 -0700 [thread overview]
Message-ID: <20201016174431.00003979@intel.com> (raw)
In-Reply-To: <20201016224502.wztzj45gxepygzqd@skbuf>
Vladimir Oltean wrote:
> On Fri, Oct 16, 2020 at 02:36:25PM -0700, Jesse Brandeburg wrote:
> > > Signed-off-by: zhudi <zhudi21@huawei.com>
> >
> > Kernel documentation says for you to use your real name, please do so,
> > unless you're a rock star and have officially changed your name to
> > zhudi.
I apologize for seeming off-putting, my goal was to add a little levity
here, but I know that email does a bad job of transmitting my intent,
and I will do better.
>
> Well, his real name is probably 朱棣, and the pinyin transliteration
> system doesn't really insist on separating 朱 (zhu) from 棣 (di), or on
> capitalizing any of twose words, so I'm not sure what your point is.
> Would you prefer his sign-off to read 朱棣 <zhudi21@huawei.com>?
Ah, thanks Vladimir for explaining the difference. If this is common
parlance for commit messages from our Chinese developers, please forgive
me, I'm trying to balance obvious correctness against typical usage.
I'll adjust my expectations for single word names, thanks!
Jesse
next prev parent reply other threads:[~2020-10-17 5:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 2:02 [PATCH] rtnetlink: fix data overflow in rtnl_calcit() zhudi
2020-10-16 21:36 ` Jesse Brandeburg
2020-10-16 22:45 ` Vladimir Oltean
2020-10-17 0:44 ` Jesse Brandeburg [this message]
2020-10-19 1:35 ` 答复: " zhudi (J)
2020-10-17 12:34 ` Michal Kubecek
2020-10-18 18:41 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2020-10-19 1:09 zhudi (J)
2020-10-19 1:59 zhudi (J)
2020-10-19 17:15 ` Jakub Kicinski
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=20201016174431.00003979@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rose.chen@huawei.com \
--cc=zhudi21@huawei.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 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.