linux-next: Tree for Aug 18

Mark Brown <[email protected]>
Newsgroups org.kernel.vger.linux-next,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
Hi all,

Changes since 20260817:

The clk tree lost it's build failure.

The net-next tree acquired multiple conflicts with the net tree.

The block tree triggered a latent issue in the fuse tree for which I
applied a fix.

There was a build failure almost certainly due to the efi tree in the
final build which I ignored.

Non-merge commits (relative to Linus' tree): 14499
 12548 files changed, 856846 insertions(+), 254055 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 429 trees (counting Linus' and 133 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.
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmqExz0ACgkQJNaLcl1U
h9ApMwf/bZafS4GFrPZpoKP65mJcty98gYlLqi9KkG0yNBtkFPOaESKjZCMxhUj7
s123qsI8ZJ3qQ5hAmNU2Wsd6dJlY7IEjGHajw/GMoPNM8MwqRDAGi46wL5sq2qnX
AZ56w2Z8H70svjL228pxUWJdQAVq2V9a96oTh2FcKDOcOw6pMJc+2pik1zlpqAOa
aMADvTm8CTeoUYZNy8OOwxBdq8J/VkYb3D0m8frucp2G1Qi71JMFbt78/TDK+xrj
Z/bB9ISQxselp2qFE+diH8LMgkFXNmN/EhGtzn5eMe6ZyBQ3ndYGdG4TJyCm+Pfx
SOH45waaVhC0b7c90f7nbAJceKKg6Q==
=HSK6
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.