From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.17-rc1
Date: Mon, 11 Aug 2025 15:21:05 +0200 [thread overview]
Message-ID: <aJnuQXzFxiFPkk6T@black.igk.intel.com> (raw)
In-Reply-To: <CAHk-=wgb=B_pGPSTw9y4Fw82y5V_mvzJp_0XcWanz7YRR5vkXA@mail.gmail.com>
On Sun, Aug 10, 2025 at 08:08:47PM +0300, Linus Torvalds wrote:
> So two weeks have passed, and depending on how you see it, rc1 is
> either earlier than usual (it's only Sunday morning back home in the
> usual timezone) or later than usual (because it's getting to be Sunday
> evening here in Finland where I'm cutting the release). I decided to
> basically split the difference on my usual "early Sunday afternoon"
> schedule.
>
> Anyway, due to travels, I wanted to do most of the heavy lifting the
> first week, and I can happily report that that part worked out well. I
> wouldn't want to do this most merge windows, but the bulk of the work
> was done before travel, and that meant that the straggler pulls were
> manageable while traveling. Thanks to everybody who got their pulls in
> early - you know who you are.
>
> And the late stragglers then got a slightly more annoyed Linus as a
> result. Sorry about that.
>
> Anyway, the merge window did end up looking fairly healthy, despite me
> having to go through a couple of bisections for trouble spots (one
> during travels with a laptop - not optimal, but thankfully it was at
> least one of the "reliable symptoms that bisect right to the culprit"
> kind). The stats look pretty normal both in patch size and in number
> of commits. That number being large enough that - as always - you only
> get the mergelog below as a kind of "view from 10,000ft" of the
> development process this time around.
>
> Please do get started testing and fixing,
FWIW, it's broken in c couple of places for `make W=1` builds, details below.
ext4:
commit 261a2abe20b0 ("ext4: fix unused variable warning in ext4_init_new_dir")
in Linux Next, but missed rc1
timers, etc (clang only):
discussion and partial fix is here
https://lore.kernel.org/all/aIo18KZpmKuR4hVZ@black.igk.intel.com/
https://lore.kernel.org/lkml/20250804220955.1453135-1-dan.j.williams@intel.com/
(haven't tested full allyesconfig and allmodconfig, though)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-08-11 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 17:08 Linux 6.17-rc1 Linus Torvalds
2025-08-11 13:21 ` Andy Shevchenko [this message]
2025-08-11 13:23 ` Andy Shevchenko
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=aJnuQXzFxiFPkk6T@black.igk.intel.com \
--to=andriy.shevchenko@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.