From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>
Subject: Re: linux-next: boot failure after merge of the akpm tree
Date: Fri, 31 May 2019 13:41:03 +1000 [thread overview]
Message-ID: <20190531134103.6fc980d9@canb.auug.org.au> (raw)
In-Reply-To: <1559269507.z7w3zfjexi.astroid@bobo.none>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Hi all,
On Fri, 31 May 2019 12:27:58 +1000 Nicholas Piggin <npiggin@gmail.com> wrote:
>
> > I have reverted
> >
> > c353e2997976 ("mm/vmalloc: hugepage vmalloc mappings")
> > a826492f28d9 ("mm: move ioremap page table mapping function to mm/")
> >
> > (and my fix up) for today and things seem to work (if only because the
> > BUG() has been removed :-)).
>
> Good to know, maybe I didn't test powerpc without later enabling
> patches...
>
> The series also has a compile bug on ARM I have to work out, so
> yeah drop those for now, I'll post a v2. The large system map patches
> that I posted in that series can stay I think.
OK, I have removed them from the akpm-current tree today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-31 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 6:17 linux-next: boot failure after merge of the akpm tree Stephen Rothwell
2019-05-31 2:27 ` Nicholas Piggin
2019-05-31 3:41 ` Stephen Rothwell [this message]
2021-11-30 7:46 Stephen Rothwell
2021-11-30 16:21 ` Luis Chamberlain
2021-12-01 19:13 ` Luis Chamberlain
2021-12-01 19:28 ` Luis Chamberlain
2021-12-01 21:44 ` Stephen Rothwell
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=20190531134103.6fc980d9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=urezki@gmail.com \
/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).