linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs
Date: Thu, 23 Jul 2020 13:02:12 +0000	[thread overview]
Message-ID: <20200723130212.BACDC20768@mail.kernel.org> (raw)
In-Reply-To: <1595468942-29687-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.10, v5.4.53.

v5.7.10: Failed to apply! Possible dependencies:
    01c0bfe061f3 ("mm: rename gfpflags_to_migratetype to gfp_migratetype for same convention")
    16867664936e ("mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations")
    3334a45eb9e2 ("mm/page_alloc: use ac->high_zoneidx for classzone_idx")
    3f08a302f533 ("mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP option")
    854e8848c584 ("mm: clean up free_area_init_node() and its helpers")
    97a225e69a1f ("mm/page_alloc: integrate classzone_idx and high_zoneidx")

v5.4.53: Failed to apply! Possible dependencies:
    01c0bfe061f3 ("mm: rename gfpflags_to_migratetype to gfp_migratetype for same convention")
    16867664936e ("mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations")
    3334a45eb9e2 ("mm/page_alloc: use ac->high_zoneidx for classzone_idx")
    34dc0ea6bc96 ("dma-direct: provide mmap and get_sgtable method overrides")
    3f08a302f533 ("mm: remove CONFIG_HAVE_MEMBLOCK_NODE_MAP option")
    854e8848c584 ("mm: clean up free_area_init_node() and its helpers")
    97a225e69a1f ("mm/page_alloc: integrate classzone_idx and high_zoneidx")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha


  reply	other threads:[~2020-07-23 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  1:49 [PATCH v2] mm/page_alloc: fix memalloc_nocma_{save/restore} APIs js1304
2020-07-23 13:02 ` Sasha Levin [this message]
2020-07-24  1:08 ` Andrew Morton
2020-07-24  2:23   ` Joonsoo Kim
2020-07-24  2:36     ` Andrew Morton
2020-07-24  3:04       ` Joonsoo Kim
2020-07-24  3:14         ` Andrew Morton
2020-07-24  3:32           ` 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=20200723130212.BACDC20768@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 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).