From: Mark Brown <broonie@kernel.org>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Tree for Sep 25
Date: Thu, 25 Sep 2025 17:22:05 +0100 [thread overview]
Message-ID: <aNVsLfsG-PWbf2cg@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
Hi all,
There will be no releases next Tuesday and Wednesday, and Monday might
not happen depending on how things go.
Changes since 20250924:
The ksmbd tree has a missing signoff.
The ksmbd tree gained a conflict with the cifs tree.
The vfs tree gained a conflict with the vfs-brauner tree.
The riscv tree gained a conflict with the mm-hotfixes tree.
The arm64 tree gained a conflict with the kbuild tree.
The tip tree gained a conflict with the bpf-next tree.
The kspp tree gained a conflict with the s390 tree.
Non-merge commits (relative to Linus' tree): 11065
11166 files changed, 534210 insertions(+), 205637 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There is also the merge.log file in the Next
directory. Between each merge, the tree was built with an arm64
defconfig, an allmodconfig for x86_64, a multi_v7_defconfig for arm and
a native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and
pseries_le_defconfig and i386, arm64, s390, sparc and sparc64 defconfig
and htmldocs. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).
Below is a summary of the state of the merge.
I am currently merging 407 trees (counting Linus' and 406 trees of bug
fix patches pending for the current release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-09-25 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 16:22 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-25 3:05 linux-next: Tree for Sep 25 Stephen Rothwell
2023-09-25 4:52 Stephen Rothwell
2020-09-25 10:55 Stephen Rothwell
2019-09-26 2:21 Mark Brown
2018-09-25 5:39 Stephen Rothwell
2015-09-25 5:04 Stephen Rothwell
2014-09-25 8:34 Stephen Rothwell
2013-09-25 4:43 Stephen Rothwell
2013-09-26 0:47 ` Joe Perches
2013-10-03 13:30 ` Fengguang Wu
2013-10-03 16: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=aNVsLfsG-PWbf2cg@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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