From: Ingo Molnar <mingo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
Valentin Schneider <valentin.schneider@arm.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: qemu boot failure after merge of the tip tree
Date: Mon, 15 Feb 2021 10:56:51 +0100 [thread overview]
Message-ID: <20210215095651.GC2185387@gmail.com> (raw)
In-Reply-To: <20210210155339.49415f2e@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Peter,
>
> On Mon, 1 Feb 2021 15:40:12 +0100 Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Mon, Feb 01, 2021 at 01:04:30PM +0000, Valentin Schneider wrote:
> > > On 01/02/21 20:09, Stephen Rothwell wrote:
> > > > Hi all,
> > > >
> > >
> > > Hi Stephen,
> > >
> > > > After merging the tip tree, today's linux-next qemu boot test (powerpc
> > > > pseries_le_defconfig) failed like this:
> > >
> > > In case you haven't seen it, Dietmar did the dirty work and fixed my fail
> > > at
> > >
> > > http://lore.kernel.org/r/6000e39e-7d28-c360-9cd6-8798fd22a9bf@arm.com
> >
> > Right, picked that up, I'll try and push it before the next next ;-)
>
> This fix has not reached the tip auto-latest branch yet and so is not in
> linux-next.
This fix should be there now as:
e972d92d52a1: ("sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa()")
Thanks,
Ingo
next prev parent reply other threads:[~2021-02-15 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 9:09 linux-next: qemu boot failure after merge of the tip tree Stephen Rothwell
2021-02-01 13:04 ` Valentin Schneider
2021-02-01 14:40 ` Peter Zijlstra
2021-02-10 4:53 ` Stephen Rothwell
2021-02-15 9:56 ` Ingo Molnar [this message]
2021-02-15 9:59 ` 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=20210215095651.GC2185387@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.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