From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context
Date: Tue, 21 Jul 2020 14:20:08 +0000 [thread overview]
Message-ID: <20200721142009.676A920714@mail.kernel.org> (raw)
In-Reply-To: <1595220978-9890-1-git-send-email-iamjoonsoo.kim@lge.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: d7fefcc8de91 ("mm/cma: add PF flag to force non cma alloc").
The bot has tested the following trees: v5.7.9, v5.4.52.
v5.7.9: Failed to apply! Possible dependencies:
01c0bfe061f30 ("mm: rename gfpflags_to_migratetype to gfp_migratetype for same convention")
16867664936e3 ("mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations")
3334a45eb9e2b ("mm/page_alloc: use ac->high_zoneidx for classzone_idx")
63b44f01f1974 ("include/linux/sched/mm.h: optimize current_gfp_context()")
97a225e69a1f8 ("mm/page_alloc: integrate classzone_idx and high_zoneidx")
a65064938b815 ("page_alloc: consider highatomic reserve in watermark fast")
v5.4.52: Failed to apply! Possible dependencies:
01c0bfe061f30 ("mm: rename gfpflags_to_migratetype to gfp_migratetype for same convention")
16867664936e3 ("mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations")
3334a45eb9e2b ("mm/page_alloc: use ac->high_zoneidx for classzone_idx")
5644e1fbbfe15 ("mm/vmscan.c: fix data races using kswapd_classzone_idx")
63b44f01f1974 ("include/linux/sched/mm.h: optimize current_gfp_context()")
97a225e69a1f8 ("mm/page_alloc: integrate classzone_idx and high_zoneidx")
a65064938b815 ("page_alloc: consider highatomic reserve in watermark fast")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-07-21 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 4:56 [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context js1304
2020-07-20 4:56 ` [PATCH v2 2/4] mm/gup: restrict CMA region by using allocation scope API js1304
2020-07-20 4:56 ` [PATCH v2 3/4] mm/hugetlb: make hugetlb migration callback CMA aware js1304
2020-07-20 4:56 ` [PATCH v2 4/4] mm/gup: use a standard migration target allocation callback js1304
2020-07-20 23:16 ` [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context Andrew Morton
2020-07-20 23:23 ` Andrew Morton
2020-07-21 3:33 ` Joonsoo Kim
2020-07-21 14:20 ` Sasha Levin [this message]
2020-07-23 1:53 ` Joonsoo Kim
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=20200721142009.676A920714@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.