linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	mm-commits@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org,
	sfr@canb.auug.org.au, broonie@kernel.org,
	Minchan Kim <minchan@kernel.org>
Subject: Re: mmotm 2016-02-03-16-36 uploaded
Date: Thu, 4 Feb 2016 18:16:02 +0100	[thread overview]
Message-ID: <20160204171601.GJ14425@dhcp22.suse.cz> (raw)
In-Reply-To: <20160204171054.GI14425@dhcp22.suse.cz>

On Thu 04-02-16 18:10:54, Michal Hocko wrote:
> On Fri 05-02-16 02:02:08, Joonsoo Kim wrote:
> > 2016-02-05 1:57 GMT+09:00 Michal Hocko <mhocko@kernel.org>:
> > > [CCing Minchan]
> > >
> > > I am getting many compilation errors if !CONFIG_COMPACTION and
> > > CONFIG_MEMORY_ISOLATION=y. I didn't get to check what has hanged in that
> > > regards because this code is quite old but the previous mmotm seemed ok,
> > > maybe some subtle change in my config?
> > 
> > It would be caused by Vlastimil's "mm, hugetlb: don't require CMA for
> > runtime gigantic pages".
> > 
> > https://lkml.org/lkml/2016/2/3/841
> > 
> > Fix is already there.
> 
> What would be the fix? Maybe I have missed it in the current mmotm...

Ohh, v2, I should have read the rest of the thread.
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2016-02-04 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04  0:37 mmotm 2016-02-03-16-36 uploaded akpm
2016-02-04 16:57 ` Michal Hocko
2016-02-04 17:02   ` Joonsoo Kim
2016-02-04 17:10     ` Michal Hocko
2016-02-04 17:16       ` Michal Hocko [this message]

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=20160204171601.GJ14425@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=js1304@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).