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 22
Date: Mon, 22 Sep 2025 12:22:26 +0200 [thread overview]
Message-ID: <aNEjYlO0jQdisB3O@finisterre.sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]
Hi all,
There will likely be some missing -next releases Monday to Wednesday
this week, normal operation will resume on Thursday.
Changes since 20250919:
The vfs tree gained a conflict with the vfs-brauner tree.
The rockchip tree gained a conflict with the arm-soc tree.
The fs-next tree gained a conflict with the arm64 tree.
The bluteooth tree gained a conflict with the origin tree.
The kvm-x86 tree gained a conflict with the tip tree.
The char-misc tree gained a conflict with the drm tree.
The char-misc tree gained a conflict with the tip tree.
The gpio-brgl tree gained a conflict with the mfd tree.
The bitmap tree gained a conflict with the char-misc and drm trees.
Non-merge commits (relative to Linus' tree): 10380
10610 files changed, 506992 insertions(+), 197129 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-22 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 10:22 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-22 6:07 linux-next: Tree for Sep 22 Stephen Rothwell
2020-09-22 9:49 Stephen Rothwell
2017-09-22 4:53 Stephen Rothwell
2016-09-22 6:11 Stephen Rothwell
2015-09-22 4:12 Stephen Rothwell
2014-09-22 7:12 Stephen Rothwell
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=aNEjYlO0jQdisB3O@finisterre.sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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