From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.15-rc3
Date: Mon, 27 Sep 2021 18:31:28 -0400 [thread overview]
Message-ID: <20210927182647-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wiuGKOBvgje56X-EdOp4mnoz4C2nM1ML6DqRFfsptai3w@mail.gmail.com>
On Mon, Sep 27, 2021 at 11:55:52AM -0700, Linus Torvalds wrote:
> On Mon, Sep 27, 2021 at 4:05 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > On Sun, Sep 26, 2021 at 02:21:52PM -0700, Linus Torvalds wrote:
> > > So after a somewhat rocky merge window and second rc, things are now
> > > actually looking pretty normal for rc3. Knock wood.
> > >
> > > There are fixes all over, and the statistics look fairly regular, with
> > > drivers dominating as they should (since they are most of the tree).
> > > And outside of drivers, we have a fairly usual mix of changes -
> > > architecture fixes, networking, filesystems, and tooling (the latter
> > > being mostly kvm selftests).
> > >
> > > Shortlog appended, it's not too long and easy to scan through to get a
> > > flavor for the details if you happen to care.
> > >
> > > Please do give it a whirl,
> > >
> >
> > Build results:
> > total: 153 pass: 152 fail: 1
> > Failed builds:
> > mips:allmodconfig
>
> Gaah. I assume this is the
>
> arch/mips/include/asm/sibyte/bcm1480_scd.h:261: error:
> "M_SPC_CFG_CLEAR" redefined
>
> thing still.
>
> It's been pending too long in the mips tree, I'll just take the patch
> directly and finally empty your queue of build failures.
>
> > Qemu test results:
> > total: 480 pass: 479 fail: 1
> > Failed tests:
> > sparc64:sun4u:nodebug:smp:virtio-pci:net,i82559er:hd
>
> And going back to your -rc1 email, I see
>
> "The qemu runtime failure bisects to commit 694a1116b405 ("virtio: Bind
> virtio device to device-tree node"), and reverting that commit fixes the
> problem. With that patch applied, the virtio block device does not
> instantiate on sparc64. This results in a crash since that is where the
> test is trying to boot from"
>
> That commit 694a1116b405 doesn't revert cleanly, but the conflict is
> trivial (we've removed a "return 0" since then).
>
> I've added the guilty parties to the participants list, but if this
> test failure remains in rc4 I'll just do that revert at that point.
Just sent a pull with a fix for that.
> > Almost there ...
>
> Almost.
>
> Linus
next prev parent reply other threads:[~2021-09-27 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 21:21 Linux 5.15-rc3 Linus Torvalds
2021-09-27 11:05 ` Guenter Roeck
2021-09-27 18:55 ` Linus Torvalds
2021-09-27 20:09 ` Thomas Bogendoerfer
2021-09-27 20:46 ` Linus Torvalds
2021-09-30 13:42 ` Guenter Roeck
2021-09-27 22:31 ` Michael S. Tsirkin [this message]
2021-09-27 20:48 Sedat Dilek
2021-09-27 21:47 ` Jason Gunthorpe
2021-09-27 21:48 ` Nick Desaulniers
2021-09-27 21:49 ` Sedat Dilek
2021-10-01 15:44 ` Sedat Dilek
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=20210927182647-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=torvalds@linux-foundation.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).