From: Andrew Morton <akpm@linux-foundation.org>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: gourry@gourry.net, harry.yoo@oracle.com,
ying.huang@linux.alibaba.com, honggyu.kim@sk.com,
yunjeong.mun@sk.com, gregkh@linuxfoundation.org,
rakie.kim@sk.com, rafael@kernel.org, lenb@kernel.org,
dan.j.williams@intel.com, Jonathan.Cameron@huawei.com,
dave.jiang@intel.com, horen.chuang@linux.dev, hannes@cmpxchg.org,
osalvador@suse.de, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-mm@kvack.org,
kernel-team@meta.com
Subject: Re: [PATCH v9] mm/mempolicy: Weighted Interleave Auto-tuning
Date: Tue, 20 May 2025 11:37:13 -0700 [thread overview]
Message-ID: <20250520113713.9b28c705b421c8bd3a51ac45@linux-foundation.org> (raw)
In-Reply-To: <20250520181125.4155631-1-joshua.hahnjy@gmail.com>
On Tue, 20 May 2025 11:11:24 -0700 Joshua Hahn <joshua.hahnjy@gmail.com> wrote:
> > Honggyu's Reviewed-by is the only change I'm seeing between v8 and v9,
> > which is unexpected?
> >
>
> Hello Andrew,
>
> The code cleanups & wordsmithing were part of the fixlets that I submitted,
> so if you are diffing against the version of v8 with the fixlets already in,
> all you should see as diffs are Honggyu's review and test tag, as well as
> Ying's review tag.
>
> I was not very familiar with the fixlet process, so I imagined that I needed
> so submit a new fixlet to add the 3 tags. If that is not the case (and you
> can just change the tags without adding a new fixlet) perhaps we can keep
> v8, just with the additional tags so we can keep the patch in the unstable
> branch?
Yes, while the patch is in mm-unstable I frequently update changelogs as
acks come in, as people provide testing results etc etc.
next prev parent reply other threads:[~2025-05-20 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 14:12 Joshua Hahn
2025-05-20 17:53 ` Andrew Morton
2025-05-20 18:11 ` Joshua Hahn
2025-05-20 18:37 ` Andrew Morton [this message]
2025-05-20 19:00 ` Joshua Hahn
2025-05-21 13:04 ` David Hildenbrand
2025-05-21 15:37 ` Joshua Hahn
2025-05-21 15:40 ` David Hildenbrand
2025-05-21 13:38 ` Oscar Salvador
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=20250520113713.9b28c705b421c8bd3a51ac45@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=honggyu.kim@sk.com \
--cc=horen.chuang@linux.dev \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=rakie.kim@sk.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yunjeong.mun@sk.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