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 27
Date: Fri, 27 Mar 2026 22:06:00 +0000 [thread overview]
Message-ID: <acb_SCAzAHPms4S3@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]
Hi all,
Changes since 20260326:
The vfs-brauner tree acquired a conflict with the exfat tree.
The vfs-brauner tree acquired a conflict with the ext4 tree.
The arm64 tree acquired a conflict with the kvm-arm tree.
The exfat tree acquired a semantic conflict with a mm change which I
applied a fixup for.
The dma-mapping tree acquired a build failure, I used the version from
next-20260326 instead.
The pci tree acquired a build failure, I used the version from
next-20260326 instead.
The drm tree acquired multiple conflicts with the drm-fixes tree.
The drm tree acquired a conflict with the origin tree.
The tip tree acquired a conflict with the mm-unstable tree.
The tracing tree acquired a build failure in the final build.
Non-merge commits (relative to Linus' tree): 9270
8901 files changed, 537418 insertions(+), 164520 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 124 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-27 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 22:06 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-27 9:05 linux-next: Tree for Mar 27 Stephen Rothwell
2024-03-27 3:06 Stephen Rothwell
2023-03-27 1:17 Stephen Rothwell
2020-03-27 8:07 Stephen Rothwell
2020-03-27 15:52 ` Randy Dunlap
2020-03-27 17:24 ` Al Viro
2019-03-27 3:50 Stephen Rothwell
2018-03-27 9:02 Stephen Rothwell
2017-03-27 5:29 Stephen Rothwell
2016-03-27 10:28 Stephen Rothwell
2015-03-27 8:26 Stephen Rothwell
2014-03-27 7:30 Stephen Rothwell
2013-03-27 5:12 Stephen Rothwell
2012-03-27 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=acb_SCAzAHPms4S3@sirena.co.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