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 Jun 2
Date: Wed, 3 Jun 2026 08:16:39 +0100 [thread overview]
Message-ID: <ah_U18GJNrYGZ8HS@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]
Hi all,
Changes since 20260601:
The btrfs tree acquired a conflict with the btrfs-fixes tree.
The vfs-brauner tree lost it's build failure.
The kbuild tree acquired a conflict with the clang-fixes tree.
The jc_docs tree acquired a conflict with the kbuild tree.
The imx-mxs tree acquired a build failure, I used the version from
next-20260601.
The v4l-dvb tree acquired a conflict with the origin tree.
The security tree gained a build failure due to an interaction with the
bpf-next tree for which I applied a revert.
The cxl tree acquired a conflict with the nvdimm tree.
Non-merge commits (relative to Linus' tree): 9287
10254 files changed, 545708 insertions(+), 202987 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at https://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 423 trees (counting Linus' and 130 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-06-03 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 7:16 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-02 4:01 linux-next: Tree for Jun 2 Stephen Rothwell
2022-06-02 4:29 Stephen Rothwell
2021-06-02 6:49 Stephen Rothwell
2020-06-02 10:37 Stephen Rothwell
2017-06-02 5:52 Stephen Rothwell
2016-06-02 4:51 Stephen Rothwell
2015-06-02 11:39 Stephen Rothwell
2014-06-02 9:27 Stephen Rothwell
2014-06-02 9:30 ` 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=ah_U18GJNrYGZ8HS@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