From: Matthew Wilcox <willy@infradead.org>
To: Jerome Glisse <jglisse@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm: fix maxnode for mbind(), set_mempolicy() and migrate_pages()
Date: Sat, 20 Jul 2024 18:55:52 +0100 [thread overview]
Message-ID: <Zpv6KNYjZcBuQfEk@casper.infradead.org> (raw)
In-Reply-To: <20240720173543.897972-1-jglisse@google.com>
On Sat, Jul 20, 2024 at 10:35:43AM -0700, Jerome Glisse wrote:
> You can tested with any of the three program below:
Do we really need three programs in the commit message, for a total of
287 lines for a one-line change?
next prev parent reply other threads:[~2024-07-20 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 17:35 [PATCH] mm: fix maxnode for mbind(), set_mempolicy() and migrate_pages() Jerome Glisse
2024-07-20 17:55 ` Matthew Wilcox [this message]
2024-07-22 21:21 ` Gregory Price
[not found] ` <0c390494-e6ba-4cde-aace-cd726f2409a1@redhat.com>
2024-07-23 16:19 ` Jerome Glisse
2024-07-23 16:33 ` Jerome Glisse
2024-07-23 17:37 ` David Hildenbrand
2024-07-23 18:24 ` David Hildenbrand
2024-07-24 4:15 ` Jerome Glisse
2024-07-24 6:27 ` David Hildenbrand
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=Zpv6KNYjZcBuQfEk@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jglisse@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).