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 Mar 11
Date: Wed, 11 Mar 2026 16:19:35 +0000 [thread overview]
Message-ID: <abGWF_ffdwObpfRh@sirena.org.uk> (raw)
Hi all,
Changes since 20260310:
The tenstorrent-clk and tenstorrent-clk-fixes trees were added.
The drm-xe tree acquired a conflict with the mm-hotfixes tree.
The drm-xe tree acquired a build failure, I used the version from
20260310 instead.
The audit tree acquired a conflict with the vfs-brauner tree.
The kvm-x86 tree acquired a conflict with the mm-unstable tree.
The efi lost it's build failure.
The kvm-arm tree gained an arm64 allyesconfig build failure which was
ignored for today.
Non-merge commits (relative to Linus' tree): 5131
5387 files changed, 343515 insertions(+), 94807 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 a defconfig
for arm64, an allmodconfig for x86_64, a multi_v7_defconfig for arm,
an arm64 build of various kselftests, a KUnit build and run on arm64,
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,
arm64 allyesconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig and pseries_le_defconfig and i386, s390, sparc and
sparc64 defconfig and htmldocs.
Below is a summary of the state of the merge.
I am currently merging 411 trees (counting Linus' and 123 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 Paul Gortmaker for triage and bug fixes.
next reply other threads:[~2026-03-11 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 16:19 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 11:18 linux-next: Tree for Mar 11 Stephen Rothwell
2021-03-11 5:14 Stephen Rothwell
2020-03-11 8:01 Stephen Rothwell
2016-03-11 5:43 Stephen Rothwell
2015-03-11 5:35 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=abGWF_ffdwObpfRh@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