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 6.15-rc3
Date: Mon, 21 Apr 2025 06:20:41 -0700 [thread overview]
Message-ID: <3f135f66-4633-4a96-86a4-9d89cfecadbc@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgjZ4fzDKogXwhPXVMA7OmZf9k0o1oB2FJmv-C1e=typA@mail.gmail.com>
On Sun, Apr 20, 2025 at 02:01:49PM -0700, Linus Torvalds wrote:
> There's absolutely nothing of huge note here as far as I can tell.
> Just a fair number of small fixes all over the place - the biggest
> changes are to fix some ublk driver issues, and the related selftests
> for same. The rest is generally one- or few-lines.
>
> So everything looks fine, and while the merge window was fairly big,
> that doesn't seem to have resulted in any particular pain. At least so
> far. Knock wood.
>
For v6.15-rc3-1-g9d7a0577c9db:
Build results:
total: 162 pass: 158 fail: 4
Failed builds:
openrisc:allmodconfig
parisc:allmodconfig
x86_64:allyesconfig
xtensa:allmodconfig
Qemu test results:
total: 635 pass: 627 fail: 8
Failed tests:
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:ext2
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:erofs
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:f2fs
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:ext2
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:erofs
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:f2fs
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:btrfs
mipsel64:boston:64r6el_defconfig:notests:nonet:smp:ide:cd
Unit test results:
pass: 594143 fail: 0
There is a new build failure, affecting openrisc, parisc, and xtensa.
Example from parisc:
Building parisc:allmodconfig ... failed
--------------
Error log:
ERROR: modpost: "__divdi3" [fs/xfs/xfs.ko] undefined!
ERROR: modpost: "__umoddi3" [fs/xfs/xfs.ko] undefined!
ERROR: modpost: "__moddi3" [fs/xfs/xfs.ko] undefined!
ERROR: modpost: "__udivdi3" [fs/xfs/xfs.ko] undefined!
Commit 845abeb1f06a ("xfs: add tunable threshold parameter for triggering
zone GC") introduced a 64-bit divide operation. I reported this to the
author, and a fix is in discussion.
Other than that, there is the known allyesconfig build failure for
x86_64:allyesconfig. I submitted a number of different proposals for
fixing it. We'll see if one of them makes it.
The fix for the mipsel64 test failure is known and will hopefully be pushed
soon.
Guenter
next prev parent reply other threads:[~2025-04-21 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 21:01 Linus Torvalds
2025-04-20 23:03 ` Linus Torvalds
2025-04-21 13:20 ` Guenter Roeck [this message]
2025-04-22 23:01 ` Dave Airlie
2025-04-22 23:37 ` Alexei Starovoitov
2025-04-23 0:12 ` Shakeel Butt
2025-04-23 0:54 ` Michael Larabel
2025-04-23 8:42 ` Vlastimil Babka
2025-04-23 13:57 ` Michael Larabel
2025-04-23 15:41 ` Alexei Starovoitov
2025-04-23 16:05 ` Linus Torvalds
2025-04-23 7:14 ` Vlastimil Babka
2025-04-23 8:03 ` Vlastimil Babka
2025-04-23 8:08 ` Vlastimil Babka
2025-04-23 14:38 ` Michael Larabel
2025-04-23 15:06 ` Alexei Starovoitov
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=3f135f66-4633-4a96-86a4-9d89cfecadbc@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®