From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Huang, Ying" <ying.huang@intel.com>,
kernel test robot <yujie.liu@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Johannes Weiner <hannes@cmpxchg.org>,
Hugh Dickins <hughd@google.com>,
Nadav Amit <nadav.amit@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-arch@vger.kernel.org, feng.tang@intel.com,
zhengjun.xing@linux.intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [mm] 5df397dec7: will-it-scale.per_thread_ops -53.3% regression
Date: Wed, 7 Dec 2022 14:20:08 -0800 [thread overview]
Message-ID: <20221207142008.e7251ad9f042ff2e89f4e866@linux-foundation.org> (raw)
In-Reply-To: <CAHk-=whkL5aM1fR7kYUmhHQHBcMUc-bDoFP7EwYjTxy64DGtvw@mail.gmail.com>
On Wed, 7 Dec 2022 12:17:47 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Andrew, here's the patch with a proper commit message. Note that my
> commit message contains the SHA1 of the original patch both in the
> explanation and in a "Fixes:" line, which I think is fine for the
> "mm-stable" branch that the original patch is in.
>
> But if you end up rebasing that mm-stable branch, then I'd ask you to
> either remove/update those commit hashes, or just fold this fix into
> the original one. Ok?
Sure.
mm-stable is supposed to be non-rebasing. I've snuck in a rebase a
couple of times early in -rc windows, but a rebase at -rc8 would
require quite a calamity.
next prev parent reply other threads:[~2022-12-07 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:59 kernel test robot
2022-12-05 20:43 ` Linus Torvalds
2022-12-06 2:02 ` Huang, Ying
2022-12-06 18:41 ` Linus Torvalds
[not found] ` <CAHk-=whjis-wTZKH20xoBW3=1qyygYoxJORxXx8ZpJbc6KtROw@mail.gmail.com>
2022-12-07 5:39 ` Huang, Ying
2022-12-07 5:54 ` Hugh Dickins
2022-12-07 20:17 ` Linus Torvalds
2022-12-07 22:20 ` Andrew Morton [this message]
2022-12-07 2:12 ` Yujie Liu
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=20221207142008.e7251ad9f042ff2e89f4e866@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=nadav.amit@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=ying.huang@intel.com \
--cc=yujie.liu@intel.com \
--cc=zhengjun.xing@linux.intel.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