From: Guenter Roeck <linux@roeck-us.net>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy'
Date: Fri, 24 Jun 2016 13:15:09 -0700 [thread overview]
Message-ID: <20160624201509.GA18324@roeck-us.net> (raw)
In-Reply-To: <20160624181325.GG1868@techsingularity.net>
On Fri, Jun 24, 2016 at 07:13:25PM +0100, Mel Gorman wrote:
> On Fri, Jun 24, 2016 at 09:46:18AM -0700, Guenter Roeck wrote:
> > > Ok, is there any chance you could test the mm-vmscan-node-lru-v8r12
> > > branch from git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
> > > please?
> > >
> > See the "testing" column at http://kerneltests.org/builders. "git describe"
> > is "v4.7-rc4-295-g572d768". Should be complete in a couple of hours.
> >
>
> That appears to be mostly passing unless I'm reading it wrong. There are a
> number of build failures but from patches pending in linux-next and mmotm
> instead of from the patch series itself.
>
For the most part, yes. arm64 crashes, though, but I have no idea if
that is because of your series or because of some inherited problem.
Can you have a look ?
Guenter
prev parent reply other threads:[~2016-06-24 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 6:05 Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy' Guenter Roeck
2016-06-24 8:39 ` Mel Gorman
2016-06-24 13:40 ` Guenter Roeck
2016-06-24 15:50 ` Mel Gorman
2016-06-24 16:46 ` Guenter Roeck
2016-06-24 18:13 ` Mel Gorman
2016-06-24 20:15 ` Guenter Roeck [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=20160624201509.GA18324@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=vbabka@suse.cz \
/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.