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 29
Date: Mon, 29 Sep 2025 16:20:26 +0100 [thread overview]
Message-ID: <aNqjuhJUX8ZuzMIj@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]
Hi all,
There will be no releases on Tueday or Wednesday, they will resume on
Thursday.
As a reminder we are in the merge window, please do not add new
non-bugfix commits.
Changes since 20250926:
The vfs-brauner tree gained a build failure for which I applied a fixup.
The net-next tree gained a conflict with the v4l-dvb tree.
The vhost tree gained a conflict with the net-next tree.
Non-merge commits (relative to Linus' tree): 11590
11571 files changed, 552562 insertions(+), 212078 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-09-29 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 15:20 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 4:25 linux-next: Tree for Sep 29 Stephen Rothwell
2023-09-29 4:28 ` Stephen Rothwell
2022-09-29 17:16 broonie
2021-09-29 6:12 Stephen Rothwell
2020-09-29 9:29 Stephen Rothwell
2017-09-29 5:48 Stephen Rothwell
2017-10-05 16:18 ` Mark Brown
2017-10-23 7:05 ` Stephen Rothwell
2016-09-29 6:32 Stephen Rothwell
2015-09-29 5:27 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=aNqjuhJUX8ZuzMIj@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