mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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-rc7
Date: Mon, 7 Mar 2022 07:00:04 -0800	[thread overview]
Message-ID: <20220307150004.GA3279416@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjkkYX8OvTv60+XvQkAK4Pg0QC0Hn-4+n7Q0t1+QWw7Sw@mail.gmail.com>

On Sun, Mar 06, 2022 at 02:41:11PM -0800, Linus Torvalds wrote:
> No surprises this week - we still have a couple of pending things, but
> everything looks under control.
> 
> Knock wood.
> 
> Last week saw the usual number of small fixes all over - with btrfs
> standing out once again. But once again it's not like it's a lot of
> changes, it's just that the rest tends to be pretty small.
> 
> "The rest" in this case is mostly networking (drivers but also some
> core fixes), misc other drivers (gpu and input, with some noise
> elsewhere) and arch updates (mostly devicetree and some kvm fixes, but
> also RISC-V and s390).
> 
> Shortlog appended - and as things stand, I expect that final 5.17 will
> be next weekend unless something surprising comes up.
> 
> Please test,
> 

Build results:
	total: 155 pass: 153 fail: 2
Failed builds:
	powerpc:skiroot_defconfig
	sparc64:allmodconfig
Qemu test results:
	total: 488 pass: 488 fail: 0

Not sure if it adds value at this point to keep reporting details,
but here they are.

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/

Fix: https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220212111349.2806972-1-mpe@ellerman.id.au/
The patch is available in linux-next. Comments in patchwork suggest
that it will only be pushed during the next merge window.

---
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: https://lore.kernel.org/lkml/20220219150836.GA1035394@roeck-us.net/T/#t
Fix: https://patchwork.ozlabs.org/project/linux-mtd/patch/20220219193600.24892-1-rogerq@kernel.org/
The patch is available in linux-next.

That, and the persistent terrible shape of linux-next, makes me wonder
if we need some kind of pre-commit and/or pre-push validation system.

Guenter

      parent reply	other threads:[~2022-03-07 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06 22:41 Linus Torvalds
2022-03-07  8:15 ` Build regressions/improvements in v5.17-rc7 Geert Uytterhoeven
2022-03-07  9:56   ` Geert Uytterhoeven
2022-03-28  7:57     ` Christophe Leroy
2022-03-07 15:00 ` 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=20220307150004.GA3279416@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®