From: Steven Price <steven.price@arm.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next 20191204: crash in mm/pagewalk.c
Date: Thu, 5 Dec 2019 13:20:10 +0000 [thread overview]
Message-ID: <20191205132009.GA48492@arm.com> (raw)
In-Reply-To: <7712.1575551749@turing-police>
On Thu, Dec 05, 2019 at 01:15:49PM +0000, Valdis Klētnieks wrote:
> On Thu, 05 Dec 2019 12:30:26 +0000, Steven Price said:
> > On Thu, Dec 05, 2019 at 12:23:02PM +0000, Valdis Kl??tnieks wrote:
> > > linux-next 20191204 dies a horrid death on my laptop while booting:
> >
> > This is due to an unfortunate conflict between my series reworking of
> > the page walk infrastructure to reuse it for kernel walks and a commit
> > by Thomas Hellstrom to allow safe modification of entries in the
> > callback. See [1] for more detail.
> >
> > I believe Andrew has dropped my series for now while I rework it to fix
> > this conflict.
>
> Thanks for the prompt response - I'll try again with today's -next if the series
> has dropped out...
The series is still in next-20191205 - but Andrew has sent me emails
saying the patch is dropped. I'm not sure how long it takes for -next to
reflect the update.
Steve
prev parent reply other threads:[~2019-12-05 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 12:23 linux-next 20191204: crash in mm/pagewalk.c Valdis Klētnieks
2019-12-05 12:30 ` Steven Price
2019-12-05 13:15 ` Valdis Klētnieks
2019-12-05 13:20 ` Steven Price [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=20191205132009.GA48492@arm.com \
--to=steven.price@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=valdis.kletnieks@vt.edu \
/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).