From: Michael Ellerman <mpe@ellerman.id.au>
To: Guenter Roeck <linux@roeck-us.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Linux 6.1-rc2
Date: Wed, 26 Oct 2022 14:44:18 +1100 [thread overview]
Message-ID: <878rl3tfjh.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20221025172239.GC968059@roeck-us.net>
Guenter Roeck <linux@roeck-us.net> writes:
> On Tue, Oct 25, 2022 at 09:41:50AM -0700, Linus Torvalds wrote:
>> On Tue, Oct 25, 2022 at 9:24 AM Guenter Roeck <linux@roeck-us.net> wrote:
>> >
>> > Build results:
>> > total: 152 pass: 152 fail: 0
>> > Qemu test results:
>> > total: 499 pass: 499 fail: 0
>>
>> Woo-hoo!
>>
>> That was quick, for once.
>>
>
> Yes, it was. I now have an even better one, with a new personal
> milestone reached (500 qemu boot tests):
>
> Build results:
> total: 152 pass: 152 fail: 0
> Qemu test results:
> total: 500 pass: 500 fail: 0
> ^^^
>
> ... after getting yet another qemu machine to boot.
>
>> > Runtime warnings
>>
>> Oh.
>>
>> Well, close enough, and those fixes are presumably pending too.
>>
>
> Let's hope so. I think I forgot to copy the ppc maintainers last week,
> so we'll see if we get some feedback on the status of those problems.
I have those in my fixes-test branch. While testing one of them I
stumbled on some issues that I've been trying to confirm are existing
and not regressions.
But I plan for those fixes to hit rc3.
cheers
prev parent reply other threads:[~2022-10-26 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 23:03 Linux 6.1-rc2 Linus Torvalds
2022-10-25 7:16 ` Build regressions/improvements in v6.1-rc2 Geert Uytterhoeven
2022-10-25 16:24 ` Linux 6.1-rc2 Guenter Roeck
2022-10-25 16:41 ` Linus Torvalds
2022-10-25 17:22 ` Guenter Roeck
2022-10-26 3:44 ` Michael Ellerman [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=878rl3tfjh.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.org \
/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