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.17-rc2
Date: Wed, 20 Aug 2025 12:53:05 -0700 [thread overview]
Message-ID: <cf5887be-46e5-423f-b434-e9f6b629f795@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wiLHgdvJQkEW-pHcUuXOBJ9JOoKcZkzMaPSW60_-Mh90A@mail.gmail.com>
On Sun, Aug 17, 2025 at 04:01:00PM -0700, Linus Torvalds wrote:
> So it's been a very calm week, and this is one of the smaller rc2
> releases we've had lately. I'm definitely not complaining, since I've
> been jetlagged much of the week, but I have this suspicion that it
> just means that next week will see more noise. And I'll be traveling
> again later in the week.
>
> But hey, let's not be pessimistic. Maybe rc2 is small because this
> merge window just didn't have any real issues? Because that's bound to
> happen _eventually_, right? One day we're bound to hit that mythical
> merge window that doesn't introduce any bugs at all.
>
> This merge window wasn't _that_ good, but maybe it was simply better than most?
>
I have been a bit lazy with reporting, but that is mostly because
there is not much to report. So, yes, this merge window seems to be
better than most (at least so far).
Build results:
total: 167 pass: 167 fail: 0
Qemu test results:
total: 637 pass: 637 fail: 0
Unit test results:
pass: 640017 fail: 652
The failing unit tests are all due to the new irq unit tests.
Those also trigger some warning backtraces. Fixing those problems
is in progress; it is nothing to be concerned about at this time.
Guenter
prev parent reply other threads:[~2025-08-20 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 23:01 Linus Torvalds
2025-08-20 19:53 ` 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=cf5887be-46e5-423f-b434-e9f6b629f795@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®