From: "Huang, Ying" <ying.huang@linux.alibaba.com>
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: Honggyu Kim <honggyu.kim@sk.com>,
kernel_team@skhynix.com,
Andrew Morton <akpm@linux-foundation.org>,
gourry@gourry.net, yunjeong.mun@sk.com,
gregkh@linuxfoundation.org, 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 v8] mm/mempolicy: Weighted Interleave Auto-tuning
Date: Sat, 17 May 2025 16:26:09 +0800 [thread overview]
Message-ID: <874ixjod7i.fsf@DESKTOP-5N7EMDA> (raw)
In-Reply-To: <20250516144346.8545-1-joshua.hahnjy@gmail.com> (Joshua Hahn's message of "Fri, 16 May 2025 07:43:45 -0700")
Joshua Hahn <joshua.hahnjy@gmail.com> writes:
> On Fri, 16 May 2025 13:37:39 +0900 Honggyu Kim <honggyu.kim@sk.com> wrote:
>
> Hi Andrew,
>
> Would it be too late at this point to add Honggyu's Reviewed-by and
> Tested-by tags? He has helped test and review this series from the start,
> but I must have missed adding his tags after rebasing from v7.
>
> Sorry again for the noise, and thank you for your understanding! I'm not
> sure what the procedure looks like for commit messages... but here is
> a fixlet if that makes sense with you:
>
> Suggested-by: Yunjeong Mun <yunjeong.mun@sk.com>
> Suggested-by: Oscar Salvador <osalvador@suse.de>
> Suggested-by: Ying Huang <ying.huang@linux.alibaba.com>
> Suggested-by: Harry Yoo <harry.yoo@oracle.com>
> +Tested-by: Honggyu Kim <honggyu.kim@sk.com>
> +Reviewed-by: Honggyu Kim <honggyu.kim@sk.com>
> Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
> Co-developed-by: Gregory Price <gourry@gourry.net>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> Signed-off-by: Joshua Hahn <joshua.hahnjy@gmail.com>
>
> And I will sign this off so that you do not have to forge my signature : -)
> Signed-off-by: Joshua Hahn <joshua.hahnjy@gmail.com>
>
> Thank you again for your help, I hope you have a great day!
Feel free to add my
Reviewed-by: Huang Ying <ying.huang@linux.alibaba.com>
too :-)
[snip]
---
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2025-05-17 8:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 18:23 Joshua Hahn
2025-05-10 5:25 ` Huang, Ying
2025-05-10 18:51 ` Joshua Hahn
2025-05-11 2:58 ` Joshua Hahn
2025-05-11 12:56 ` Honggyu Kim
2025-05-12 14:14 ` Joshua Hahn
2025-05-16 4:37 ` Honggyu Kim
2025-05-16 14:43 ` Joshua Hahn
2025-05-17 8:26 ` Huang, Ying [this message]
2025-05-12 1:35 ` Huang, Ying
2025-05-12 14:25 ` Joshua Hahn
2025-05-12 22:29 ` Andrew Morton
2025-05-13 14:01 ` Joshua Hahn
2025-05-13 1:41 ` Huang, Ying
2025-05-13 13:59 ` Joshua Hahn
2025-05-19 1:56 ` Joshua Hahn
2025-05-19 22:31 ` Andrew Morton
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=874ixjod7i.fsf@DESKTOP-5N7EMDA \
--to=ying.huang@linux.alibaba.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=honggyu.kim@sk.com \
--cc=horen.chuang@linux.dev \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=kernel_team@skhynix.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=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