From: Vlastimil Babka <vbabka@suse.cz>
To: js1304@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@lge.com, Christoph Hellwig <hch@infradead.org>,
Roman Gushchin <guro@fb.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Michal Hocko <mhocko@suse.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v5 5/9] mm/migrate: make a standard migration target allocation function
Date: Mon, 13 Jul 2020 09:53:40 +0200 [thread overview]
Message-ID: <641fa691-ce77-7eae-75e5-452c0a111ae9@suse.cz> (raw)
In-Reply-To: <1594622517-20681-6-git-send-email-iamjoonsoo.kim@lge.com>
On 7/13/20 8:41 AM, js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Nit: s/make/introduce/ in the subject, is a more common verb in this context.
next prev parent reply other threads:[~2020-07-13 7:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 6:41 [PATCH v5 0/9] clean-up the migration target allocation functions js1304
2020-07-13 6:41 ` [PATCH v5 1/9] mm/page_isolation: prefer the node of the source page js1304
2020-07-13 6:41 ` [PATCH v5 2/9] mm/migrate: move migration helper from .h to .c js1304
2020-07-13 6:41 ` [PATCH v5 3/9] mm/hugetlb: unify migration callbacks js1304
2020-07-13 6:41 ` [PATCH v5 4/9] mm/migrate: clear __GFP_RECLAIM to make the migration callback consistent with regular THP allocations js1304
2020-07-13 7:36 ` Michal Hocko
2020-07-13 7:52 ` Vlastimil Babka
2020-07-14 0:44 ` Joonsoo Kim
2020-07-13 6:41 ` [PATCH v5 5/9] mm/migrate: make a standard migration target allocation function js1304
2020-07-13 7:53 ` Vlastimil Babka [this message]
2020-07-14 0:46 ` Joonsoo Kim
2020-07-13 6:41 ` [PATCH v5 6/9] mm/mempolicy: use a standard migration target allocation callback js1304
2020-07-13 6:41 ` [PATCH v5 7/9] mm/page_alloc: remove a wrapper for alloc_migration_target() js1304
2020-07-13 6:41 ` [PATCH v5 8/9] mm/memory-failure: " js1304
2020-07-13 6:41 ` [PATCH v5 9/9] mm/memory_hotplug: " js1304
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=641fa691-ce77-7eae-75e5-452c0a111ae9@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hch@infradead.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.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