From: Greg KH <gregkh@linuxfoundation.org>
To: cgel.zte@gmail.com
Cc: shuah@kernel.org, jstultz@google.com, tglx@linutronix.de,
sboyd@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
ye xingchen <ye.xingchen@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] selftests: timers: Remove the unneeded result variable
Date: Tue, 20 Sep 2022 09:46:46 +0200 [thread overview]
Message-ID: <Yylv5hbSBejJ58nt@kroah.com> (raw)
In-Reply-To: <20220920063202.215088-1-ye.xingchen@zte.com.cn>
On Tue, Sep 20, 2022 at 06:32:02AM +0000, cgel.zte@gmail.com wrote:
> From: ye xingchen <ye.xingchen@zte.com.cn>
>
> Return the value adjtimex() directly instead of storing it in another
> redundant variable.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
Once again, as this seems to keep being forgotten, you are sending
multiple patches all from the same gmail.com account, yet are claiming
they are from different people from a company that no one from that
company has agreed is actually at that company.
Then there's the whole "ignoring
Documentation/process/researcher-guidelines.rst" issues, which would
disqualify the changes anyway.
So we can not take these patches at all.
Please fix up your corporate email structures so that you can properly
submit changes to the kernel that can be verified to actually come from
your company. Otherwise they can not be accepted at all for obvious
reasons (ZTE would not want to have people claiming to work for them
that are not actually working for them, right?)
thanks,
greg k-h
prev parent reply other threads:[~2022-09-20 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 6:32 [PATCH linux-next] selftests: timers: Remove the unneeded result variable cgel.zte
2022-09-20 7:46 ` Greg KH [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=Yylv5hbSBejJ58nt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cgel.zte@gmail.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=ye.xingchen@zte.com.cn \
--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;
as well as URLs for NNTP newsgroup(s).