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.12-rc1
Date: Sun, 29 Sep 2024 17:38:02 -0700 [thread overview]
Message-ID: <d75c8f9d-8b3f-4d3e-996c-bbb9a6c240c0@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wiwVOCZsC6a4dLdb1UjL2fS_CnLNjrPL0XGFbDd9C26Cg@mail.gmail.com>
On Sun, Sep 29, 2024 at 03:51:43PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and rc1 is out - the merge window is closed.
>
> Despite conference travel (both for me and several maintainers),
> things seemed to go mostly fairly normally. There's a couple of
> notable new features in here: For one thing, PREEMPT_RT is now
> mainlined and enabled as a config option (you do need to enable
> "EXPERT" to get the question). For another, sched_ext also got merged.
>
> That said, the bulk is - as always - all the plain old regular
> updates, and that obviously means drivers dominate. We've got about
> 55% of the patch being drivers (and another 5% if you count the dts
> files). Add in 5% doc updates, and 10% tooling (mostly perf and
> selftests).
>
> That leaves about a quarter of the overall changes as core kernel
> code, split between arch updates, filesystems (yes, bcachefs, but also
> btrfs, smb sever and client, netfs updates, xfs and finally core VFS
> updates mostly in the form of 'struct fd' re-organisational cleanups).
> And MM, core networking, Rust, security layer updates etc.
>
> A little bit of everything, in other words. And nothing really looks
> all that strange. As always, the summary below is just the log of my
> merges, there's too much to list individually (some stats: 11k+
> regular commits, 850+ merges, 1700+ different authors).
>
> Let's get the testing and calming down period started, ok?
>
Fails to build on big endian systems. I'll send a patch in a minute.
Guenter
next prev parent reply other threads:[~2024-09-30 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 22:51 Linus Torvalds
2024-09-30 0:38 ` Guenter Roeck [this message]
2024-09-30 13:15 ` Jason A. Donenfeld
2024-09-30 17:22 ` Linus Torvalds
2024-09-30 19:17 ` Jason A. Donenfeld
2024-09-30 14:53 ` Build regressions/improvements in v6.12-rc1 Geert Uytterhoeven
2024-09-30 15:11 ` Geert Uytterhoeven
2024-09-30 16:26 ` Herve Codina
2024-09-30 17:01 ` Linux 6.12-rc1 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=d75c8f9d-8b3f-4d3e-996c-bbb9a6c240c0@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®