From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Deepa Dinamani <deepa.kernel@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [y2038] 412c53a680: will-it-scale.per_process_ops 11.7% improvement
Date: Thu, 5 Mar 2020 19:53:17 -0800 [thread overview]
Message-ID: <20200305195317.771bd8fd1f308172d26a51fe@linux-foundation.org> (raw)
In-Reply-To: <20200305062138.GI5972@shao2-debian>
On Thu, 5 Mar 2020 14:21:38 +0800 kernel test robot <rong.a.chen@intel.com> wrote:
> FYI, we noticed a 11.7% improvement of will-it-scale.per_process_ops due to commit:
>
>
> commit: 412c53a680a97cb1ae2c0ab60230e193bee86387 ("y2038: remove unused time32 interfaces")
That patch merely removed unused code!
next prev parent reply other threads:[~2020-03-06 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 6:21 [y2038] 412c53a680: will-it-scale.per_process_ops 11.7% improvement kernel test robot
2020-03-06 3:53 ` Andrew Morton [this message]
2020-04-20 10:36 ` [LKP] " Feng Tang
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=20200305195317.771bd8fd1f308172d26a51fe@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=rong.a.chen@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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