From: Mike Rapoport <rppt@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Su Hua <suhua.tanke@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: boot failure after merge of the memblock tree
Date: Tue, 29 Oct 2024 09:15:40 +0200 [thread overview]
Message-ID: <ZyCLnJ01aYBlSWPA@kernel.org> (raw)
In-Reply-To: <20241029072039.39d850dc@canb.auug.org.au>
On Tue, Oct 29, 2024 at 07:20:39AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Sat, 26 Oct 2024 07:36:13 +0800 Su Hua <suhua.tanke@gmail.com> wrote:
> >
> > > > diff --git a/mm/mm_init.c b/mm/mm_init.c
> > > > index 4ba5607aaf19..5a8114fb02ae 100644
> > > > --- a/mm/mm_init.c
> > > > +++ b/mm/mm_init.c
> > > > @@ -723,6 +723,9 @@ static void __meminit init_reserved_page(unsigned
> > > > long pfn, int nid)
> > > > break;
> > > > }
> > > > __init_single_page(pfn_to_page(pfn), pfn, zid, nid);
> > > > +
> > > > + if (pageblock_aligned(pfn))
> > > > + set_pageblock_migratetype(pfn_to_page(pfn), MIGRATE_MOVABLE);
> > > > }
> > > > #else
>
> This has returned, so I applied by hand the above discussed fix.
Sorry, I forgot to push :/
> --
> Cheers,
> Stephen Rothwell
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2024-10-29 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 6:39 linux-next: boot failure after merge of the memblock tree Stephen Rothwell
2024-10-23 3:20 ` Su Hua
2024-10-23 22:23 ` Stephen Rothwell
2024-10-24 3:18 ` Su Hua
2024-10-25 6:53 ` Mike Rapoport
2024-10-25 8:19 ` Su Hua
2024-10-25 8:33 ` Su Hua
2024-10-25 8:42 ` Mike Rapoport
2024-10-25 23:36 ` Su Hua
2024-10-28 20:20 ` Stephen Rothwell
2024-10-29 7:15 ` Mike Rapoport [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=ZyCLnJ01aYBlSWPA@kernel.org \
--to=rppt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=suhua.tanke@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 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.