From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Helge Deller <deller@gmx.de>
Subject: Re: Linux 6.6-rc1
Date: Tue, 12 Sep 2023 10:59:57 -0700 [thread overview]
Message-ID: <3c85e5f7-c9a4-4c77-b4e9-3b476ac6c1fb@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgfL1rwyvELk2VwJTtiLNpwxTFeFtStLeAQ-2rTRd34eQ@mail.gmail.com>
On Sun, Sep 10, 2023 at 04:53:55PM -0700, Linus Torvalds wrote:
> Here we are, two weeks later, and the merge window is closed.
>
[ ... ]
>
> Please do give it all a whirl,
>
Build results:
total: 157 pass: 151 fail: 6
Failed builds:
alpha:allmodconfig
csky:allmodconfig
m68k:allmodconfig
openrisc:allmodconfig
parisc:allmodconfig
s390:allmodconfig
Qemu test results:
total: 530 pass: 522 fail: 8
Failed qemu tests:
<all s390>
Build failures are all:
drivers/mfd/cs42l43.c:1138:12: error: 'cs42l43_runtime_resume' defined but not used [-Werror=unused-function]
drivers/mfd/cs42l43.c:1124:12: error: 'cs42l43_runtime_suspend' defined but not used [-Werror=unused-function]
Caused by commit ace6d1448138 ("mfd: cs42l43: Add support for cs42l43 core driver").
Will be fixed with
https://lore.kernel.org/r/20230822114914.340359-1-ckeepax@opensource.cirrus.com
Runtime crashes (s390):
Unable to handle kernel pointer dereference in virtual kernel address space
...
Call Trace:
kunit_next_attr_filter+0xc8/0x1c8
Caused by commit 76066f93f1df ("kunit: add tests for filtering attributes").
Will be fixed with
https://lore.kernel.org/r/20230830002116.3768675-1-davidgow@google.com
New runtime warnings:
arm:mcimx6ul-evk:
WARNING: CPU: 0 PID: 1 at drivers/regulator/core.c:2396 _regulator_put.part.0+0x1b4/0x1d8
Caused by commit 422f10adc3eb ("ASoC: wm8960: Add support for the power supplies").
Will be fixed with
https://lore.kernel.org/lkml/20230909120237.2646275-1-linux@roeck-us.net/
loongarch:
INFO: trying to register non-static key.
Caused by commit 0a6b58c5cd0d ("lockdep: fix static memory detection even
more"). No fix available as far as I know.
Guenter
next prev parent reply other threads:[~2023-09-12 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 23:53 Linus Torvalds
2023-09-11 2:38 ` linux-next: stats (Was: Linux 6.6-rc1) Stephen Rothwell
2023-09-11 9:02 ` Geert Uytterhoeven
2023-09-11 8:38 ` Build regressions/improvements in v6.6-rc1 Geert Uytterhoeven
2023-09-11 23:08 ` Randy Dunlap
2023-09-12 6:49 ` Geert Uytterhoeven
2023-09-12 7:33 ` Randy Dunlap
2023-09-12 6:39 ` Geert Uytterhoeven
2023-09-12 17:59 ` Guenter Roeck [this message]
2023-09-12 18:17 ` Linux 6.6-rc1 Linus Torvalds
2023-09-12 18:25 ` Helge Deller
2023-09-12 18:33 ` 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=3c85e5f7-c9a4-4c77-b4e9-3b476ac6c1fb@roeck-us.net \
--to=linux@roeck-us.net \
--cc=deller@gmx.de \
--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®