From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.17-rc4
Date: Sun, 13 Feb 2022 16:05:34 -0800 [thread overview]
Message-ID: <20220214000534.GA976691@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgpOhU0cU+KZHA86OsoN2BxqT4ZoTMYHDMuzbiiiKK1Eg@mail.gmail.com>
On Sun, Feb 13, 2022 at 12:29:27PM -0800, Linus Torvalds wrote:
> Things continue to look pretty normal for 5.17. Both the diffstat and
> the number of commits looks pretty much average for an rc4 release.
>
> About half the changes being to drivers (all over, but as usual gpu
> and networking is a noticeable part of driver changes), with arch
> updates showing up next (devicetree updates dominate, but there's
> "real code" changes too).
>
> Other than that, we've got filesystem fixes, core networking, tooling,
> and misc core kernel fixlets.
>
> The appended shortlog gives details as usual, nothing in here looks worrisome.
>
Build results:
total: 155 pass: 154 fail: 1
Failed builds:
powerpc:skiroot_defconfig
Qemu test results:
total: 488 pass: 487 fail: 1
Failed tests:
arm:orangepi-pc:multi_v7_defconfig:usb1:net,nic:sun8i-h3-orangepi-pc:rootfs
Nothing new here. It should be noted that the fix for the orangepi boot
failure introduces (or exposes) another problem. I reported this at
https://lore.kernel.org/linux-media/20211206131648.1521868-1-hverkuil-cisco@xs4all.nl/T/#t
Guenter
next prev parent reply other threads:[~2022-02-14 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 20:29 Linus Torvalds
2022-02-14 0:05 ` Guenter Roeck [this message]
2022-02-21 2:47 ` Guenter Roeck
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=20220214000534.GA976691@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®