From: Tony Lindgren <tony@atomide.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Michal Hocko <mhocko@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Regression still in next for drop migrate type checks
Date: Fri, 3 Nov 2017 10:57:38 -0700 [thread overview]
Message-ID: <20171103175738.GL28152@atomide.com> (raw)
In-Reply-To: <20171103103224.524541d001571f63daa8fdcc@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [171103 17:34]:
> On Fri, 3 Nov 2017 09:00:12 -0700 Tony Lindgren <tony@atomide.com> wrote:
>
> > Looks like I'm still carrying patch "mm: distinguish CMA and MOVABLE
> > isolation in has_unmovable_pages" from Michal [1] for commit e1d753dff0fa
> > ("mm: drop migrate type checks from has_unmovable_pages") and Linux next
> > has been broken for CMA for few weeks now as noted in the discussion
> > also at [1].
> >
> > What's the status of this regression? How come it's been known
> > broken for two weeks and still not fixed or reverted in next?
> > This is clearly is not suitable for "wider testing" ;)
>
> Travel to Europe and subsequent bustage in the -next tree held things
> up. Today's merge looks good so I expect to get this into Stephen
> today.
OK thanks for the update.
> In future, please feel free to send such hot fixes to Stephen.
Sure.
Tony
next prev parent reply other threads:[~2017-11-03 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 16:00 Regression still in next for drop migrate type checks Tony Lindgren
2017-11-03 17:32 ` Andrew Morton
2017-11-03 17:57 ` Tony Lindgren [this message]
2017-11-04 8:25 ` Michal Hocko
2017-11-04 8:35 ` Michal Hocko
2017-11-06 23:22 ` Tony Lindgren
2017-11-06 14:38 ` Tony Lindgren
2017-11-06 14:42 ` Michal Hocko
2017-11-07 2:20 ` Tony Lindgren
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=20171103175738.GL28152@atomide.com \
--to=tony@atomide.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mhocko@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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.