All of lore.kernel.org
 help / color / mirror / Atom feed
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 Aug 11
Date: Tue, 11 Aug 2026 17:07:09 +0100	[thread overview]
Message-ID: <antIrd2ds2OiEsl5@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]

Hi all,

Changes since 20260810:

The f2fs tree acquired a build failure, I used the version from
next-20260810 instead.

The thermal tree lost it's build failure.

The kvm-arm tree acquired a conflict with the powerpc tree.

The char-misc tree acquired a conflict with the rust tree.

The pwm tree acquired a conflict with the rust tree.

Non-merge commits (relative to Linus' tree): 13196
 11613 files changed, 638650 insertions(+), 206468 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-08-11 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 16:07 Mark Brown [this message]
2026-08-11 17:25 ` linux-next: Tree for Aug 11 (include/linux/mm.h) Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2022-08-11  2:15 linux-next: Tree for Aug 11 Stephen Rothwell
2021-08-11 11:53 Stephen Rothwell
2020-08-11  4:52 Stephen Rothwell
2017-08-11  8:36 Stephen Rothwell
2016-08-11  3:32 Stephen Rothwell
2014-08-11  5:52 Stephen Rothwell
2014-08-11 17:05 ` Guenter Roeck
2014-08-12  0:59   ` Stephen Rothwell
2014-08-12  1:08     ` Guenter Roeck
2011-08-11  6:20 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=antIrd2ds2OiEsl5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.