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.15-rc6
Date: Tue, 19 Oct 2021 13:33:20 -0700 [thread overview]
Message-ID: <20211019203320.GA748645@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjbXW13Eh6YnB4C5ghLrhJCq0u2bpSNA0JbK8eDb6o_XA@mail.gmail.com>
On Sun, Oct 17, 2021 at 08:14:59PM -1000, Linus Torvalds wrote:
> So here we are, slightly later on a Sunday than usual due to travel,
> but rc6 is out.
>
> I'd love to say that it's all looking average, but rc6 is actually
> bigger han rc5 was, and larger than normal for this time in the
> release cycle.
>
> It's not _enormously_ larger than normal, and it's not the largest rc6
> we've had, but it's still slightly worrisome. By rc6 I really do
> expect things to have started calming down.
>
> I'm hoping it's just one of those random timing effects, with a couple
> of slightly bigger pulls having come in the last week, and we'll see
> the next week being extra quiet because rc6 got some of the stuff that
> would normally have hit rc7. It happens. But let's see how this goes.
>
> The 5.15 cycle over-all remains one of the smaller cycles (at least
> counting commits), so I wouldn't have expected this to be one that
> requires an extra rc, but that may be what ends up happening unless
> the upcoming week is really nice and calm.
>
> That said, nothing in here looks _particularly_ worrisome. It really
> smells like just random timing effects to me, with networking, GPU
> drivers, and ntfs3 all having had a somewhat active week. Other than
> that it all really looks fairly normal.
>
> Full details in the shortlog below.
>
> Please give it a whirl. And let's hope for a nice calm next week and a
> smaller rc7.
>
Build results:
total: 153 pass: 149 fail: 4
Failed builds:
alpha:allmodconfig
m68k:allmodconfig
parisc:allmodconfig
s390:allmodconfig
Qemu test results:
total: 480 pass: 480 fail:
The error is:
Building alpha:allmodconfig ... failed
--------------
Error log:
<stdin>:1517:2: warning: #warning syscall clone3 not implemented [-Wcpp]
drivers/spi/spi-tegra20-slink.c:1197:12: error: 'tegra_slink_runtime_resume' defined but not used [-Werror=unused-function]
1197 | static int tegra_slink_runtime_resume(struct device *dev)
This was introduced by a bad conflict resolution between the following
two patches.
efafec27c565 spi: Fix tegra20 build with CONFIG_PM=n
2bab94090b01 spi: tegra20-slink: Declare runtime suspend and resume functions conditionally
The fix is at
https://patchwork.kernel.org/project/spi-devel-general/patch/20211013144538.2346533-1-arnd@kernel.org/
and queued in -next.
Guenter
next prev parent reply other threads:[~2021-10-19 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 6:14 Linus Torvalds
2021-10-19 20:33 ` Guenter Roeck [this message]
2021-10-25 18:07 ` Linus Torvalds
2021-10-25 19:47 ` Mark Brown
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=20211019203320.GA748645@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®