From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jinpeng Cui <cuijinpeng666@gmail.com>,
Zeal Robot <zealci@zte.com.cn>,
alan.maguire@oracle.com, ast@kernel.org, bpf@vger.kernel.org,
cui.jinpeng2@zte.com.cn, jolsa@kernel.org,
linux-kernel@vger.kernel.org, peterz@infradead.org,
stephen.s.brennan@oracle.com
Subject: Re: [PATCH linux-next] kallsyms: Use strscpy() instead of strlcpy()
Date: Fri, 21 Oct 2022 09:17:10 -0700 [thread overview]
Message-ID: <202210210915.B177280DA8@keescook> (raw)
In-Reply-To: <Y1FCiH16RIetS0hZ@kroah.com>
On Thu, Oct 20, 2022 at 02:43:52PM +0200, Greg KH wrote:
> > I am very sorry if the patches from zte.com.cn
> > in the past few months have made you angry,
> > we have decided to fix the problem you pointed out
> > as soon as possible.
> > Our company's mailbox name@zte.com.cn
> > cannot send emails to the external network,
> > so we use name@gmail.com to send patches;
>
> You all have been warned numerous times over many weeks and months and
> never responded to our emails.
>
> We have no proof that using gmail accounts is actually coming from a ZTE
> employee, so until that happens, we can not take your changes (not to
> mention the basic fact that you all keep ignoring our review comments,
> which is a good enough reason to ignore them.)
Aren't there a few solutions here?
1) Just send the emails from @gmail with matching S-o-b.
2) Send an @zte.com.cn to lkml to confirm their @gmail/@zte.com.cn mapping.
3) Fix the email systems.
--
Kees Cook
next prev parent reply other threads:[~2022-10-21 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 9:05 [PATCH linux-next] kallsyms: Use strscpy() instead of strlcpy() cuijinpeng666
2022-10-20 9:32 ` Greg KH
[not found] ` <CANhqVYZ+trZzPdB=Vd9YV53DAJt0p5LZQH-u94+VRrDQ5+w2MA@mail.gmail.com>
2022-10-20 12:43 ` Greg KH
2022-10-21 16:17 ` Kees Cook [this message]
2022-10-22 5:56 ` Greg KH
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=202210210915.B177280DA8@keescook \
--to=keescook@chromium.org \
--cc=alan.maguire@oracle.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cui.jinpeng2@zte.com.cn \
--cc=cuijinpeng666@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stephen.s.brennan@oracle.com \
--cc=zealci@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