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 Oct 2
Date: Thu, 2 Oct 2025 17:37:44 +0100 [thread overview]
Message-ID: <aN6qWFc6hIcbRU1o@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
Hi all,
Changes since 20250929:
Linus' tree gained a build failure.
The nfsd tree gained a conflict with the nfs-anna tree.
The vfs-brauner tree gained a conflict with Linus' tree.
The drm tree gained multiple conflicts with Linus' tree.
The ftrace tree gained a conflict with Linus' tree, and also a build
failure so I used the version from 20250929 instead.
The kvm tree gained a conflict with Linus' tree.
The hyperv tree gained a conflict with the fbdev tree.
Non-merge commits (relative to Linus' tree): 8092
8162 files changed, 387039 insertions(+), 145286 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.
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-10-02 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 16:37 Mark Brown [this message]
2025-10-02 20:10 ` linux-next: Tree for Oct 2 Dan Carpenter
2025-10-02 21:35 ` Miguel Ojeda
2025-10-03 7:05 ` Dan Carpenter
2025-10-03 19:16 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2024-10-02 4:50 Stephen Rothwell
2020-10-02 9:57 Stephen Rothwell
2019-10-02 4:46 Stephen Rothwell
2018-10-02 9:18 Stephen Rothwell
2015-10-02 5:27 Stephen Rothwell
2014-10-02 10:26 Stephen Rothwell
2013-10-02 15:32 Thierry Reding
2012-10-02 6:32 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=aN6qWFc6hIcbRU1o@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