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.6-rc2
Date: Mon, 18 Sep 2023 12:20:35 -0700 [thread overview]
Message-ID: <ca3ac950-db89-426e-b5af-9f8bf5f91658@roeck-us.net> (raw)
In-Reply-To: <CAHk-=whW=fV2tnAreSbtPVpJxq++pyBZa3g+cxX8_V__WSZzCg@mail.gmail.com>
On Sun, Sep 17, 2023 at 02:55:46PM -0700, Linus Torvalds wrote:
> Another week, another -rc.
>
[ ... ]
>
> Please go test,
>
No significant change / improvement since last week.
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: 530 fail: 0
Same build errors, same warnings as with 6.6-rc1.
Well, that is not entirely true. I do see a bunch of warnings in folio
code, such as
WARNING: CPU: 1 PID: 774 at include/linux/backing-dev.h:252 __folio_mark_dirty+0x318/0x350
but that is because I started testing gfs2 which always had that problem.
I am not sure if it is even worth reporting it. I did send a note to
the gfs2 mailing list and maintainers, and I won't mention it here again.
My list of pending fixes includes the following three patches.
LoongArch: Fix lockdep static memory detection
mfd: cs42l43: Use correct macro for new-style PM runtime ops
ASoC: wm8960: Fix error handling in probe
Guenter
prev parent reply other threads:[~2023-09-18 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 21:55 Linux 6.6-rc2 Linus Torvalds
2023-09-18 7:27 ` Build regressions/improvements in v6.6-rc2 Geert Uytterhoeven
2023-09-18 7:40 ` Geert Uytterhoeven
2023-09-18 19:20 ` 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=ca3ac950-db89-426e-b5af-9f8bf5f91658@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;
as well as URLs for NNTP newsgroup(s).