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, 20 Feb 2022 18:47:43 -0800 [thread overview]
Message-ID: <20220221024743.GA4097766@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: 152 fail: 3
Failed builds:
mips:malta_defconfig
powerpc:skiroot_defconfig
sparc64:allmodconfig
Qemu test results:
total: 488 pass: 427 fail: 61
Failed tests:
arm:orangepi-pc:multi_v7_defconfig:usb1:net,nic:sun8i-h3-orangepi-pc:rootfs
<almost all mips tests>
---
Building powerpc:skiroot_defconfig ... failed
--------------
arch/powerpc/kernel/stacktrace.c: In function 'handle_backtrace_ipi':
arch/powerpc/kernel/stacktrace.c:171:9: error: implicit declaration of function 'nmi_cpu_backtrace'
Introduced with commit 1614b2b11fab29 ("arch: Make ARCH_STACKWALK
independent of STACKTRACE"). Discussed at
https://lore.kernel.org/lkml/YeE2VWwHO50gFw9M@hirez.programming.kicks-ass.net/T/
Fixed with commit 5a72345e6a78 ("powerpc: Fix STACKTRACE=n build") in linux-next.
---
Building arm:orangepi-pc:multi_v7_defconfig:usb1:net,nic:sun8i-h3-orangepi-pc:rootfs ... running ........R.... failed (no root file system)
Introduced with 8df89a7cbc63 ("pinctrl-sunxi: don't call
pinctrl_gpio_direction()"). Fix posted at
https://patchwork.kernel.org/project/linux-media/patch/0f536cd8-01db-5d16-2cec-ec6d19409a49@xs4all.nl/
and in linux-next as commit 3c5412cdec9f ("pinctrl-sunxi:
sunxi_pinctrl_gpio_direction_in/output: use correct offset").
The fix exposes a lockdep splat for which a fix is posted at
https://lore.kernel.org/lkml/20220216040037.22730-1-samuel@sholland.org/
---
Building mips:malta_defconfig ... failed
------------
Error log:
net/netfilter/xt_socket.c: In function ‘socket_mt_destroy’:
net/netfilter/xt_socket.c:224:3: error: implicit declaration of function ‘nf_defrag_ipv6_disable’
This problem affects all configurations with IPV4 enabled and IPV6
disabled. Caused by commit 75063c9294fb2 ("netfilter: xt_socket: fix
a typo in socket_mt_destroy()"). Build failure reported by 0-day and
fix suggested at
https://lore.kernel.org/netdev/CANn89iLS4N4cpX+Nh9ALjf_APOPQ4-aSPSX1P6iLpda8mJS8UQ@mail.gmail.com/
Fix not posted as patch as far as I know.
---
Building sparc64:allmodconfig ... failed
--------------
Error log:
<stdin>:1517:2: warning: #warning syscall clone3 not implemented [-Wcpp]
sparc64-linux-ld: drivers/memory/omap-gpmc.o: in function `gpmc_probe_generic_child':
omap-gpmc.c:(.text.unlikely+0x14c4): undefined reference to `of_platform_device_create'
Introduced by commit 4cd335dae3cf ("mtd: rawnand: omap2: Prevent invalid
configuration and build error"). Reported at
https://lore.kernel.org/lkml/20220219150836.GA1035394@roeck-us.net/T/#t
Fix posted at
https://lore.kernel.org/all/20220219193600.24892-1-rogerq@kernel.org/t/
prev parent reply other threads:[~2022-02-21 2:47 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
2022-02-21 2:47 ` Guenter Roeck [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=20220221024743.GA4097766@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®