From: chaithco@redhat.com
To: Joshua Hahn <joshua.hahnjy@gmail.com>
Cc: muchun.song@linux.dev, osalvador@suse.de,
akpm@linux-foundation.org, david@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, arozansk@redhat.com
Subject: Re: [PATCH 1/2] mm/hugetlb: Prefer mempolicy nodes for calcuating surplus hugepage reservation
Date: Wed, 08 Jul 2026 09:39:11 -0600 [thread overview]
Message-ID: <BT4VHT.DYI921C1JF9G@redhat.com> (raw)
In-Reply-To: <20260707193358.3434034-1-joshua.hahnjy@gmail.com>
On Tue, Jul 7 2026 at 12:33:57 PM -07:00:00, Joshua Hahn
<joshua.hahnjy@gmail.com> wrote:
> On Tue, 7 Jul 2026 12:28:55 -0600 Charles Haithcock
<chaithco@redhat.com> wrote:
>
> Hi Charles, thank you for the patch, this looks good to me!
>
> Personally I like the description of the commit in the cover letter
> because it provides a bit more context. Do other reviewers have
> thoughts on this? In any case, the code LGTM : -)
Thank you! If people prefer, I can copy the cover letter contents to
the main
patch notes. Just let me know!
> BTW this is a little strange but Sashiko seems to have failed to
apply
> this patch [1] which is strange because when applying on the exact
> same commit db6ed2a3d3106 "mm/swap, PM: hibernate: atomically
replace hibernation pin"
> as Sashiko tried, it worked & compiled for me with no errors at
all...
Interesting; is this something I need to act on in any way?
>
next prev parent reply other threads:[~2026-07-08 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 18:28 [PATCH 0/2] mm/hugetlb Try to respect mempolicy when calculating surplus huge pages Charles Haithcock
2026-07-07 18:28 ` [PATCH 1/2] mm/hugetlb: Prefer mempolicy nodes for calcuating surplus hugepage reservation Charles Haithcock
2026-07-07 19:33 ` Joshua Hahn
2026-07-08 15:39 ` chaithco [this message]
2026-07-09 14:30 ` Joshua Hahn
2026-07-07 18:28 ` [PATCH 2/2] selftests/mm: add surplus hugetlb mempolicy reservation tests Charles Haithcock
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=BT4VHT.DYI921C1JF9G@redhat.com \
--to=chaithco@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arozansk@redhat.com \
--cc=david@kernel.org \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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