mirror of https://lore.kernel.org/lkml/
 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 Oct 1
Date: Fri, 2 Oct 2026 12:33:02 +0100	[thread overview]
Message-ID: <ar-WbnTc3mEdbz9C@sirena.org.uk> (raw)

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

Hi all,

Note that I will be travelling to LPC from 2nd-9th October, as a
result -next releases will be at best spotty during that time.

Changes since 20260930:

The mm tree acquired a conflict with the kvm-arm-fixes tree.

The net-next tree acquired a conflict with the net tree.

The iwlwifi-next tree acquired a conflict with the iwlwifi tree.

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

The phy-next tree acquired a conflict with the v4l-dvb tree.

The random tree acquired a conflict with the kbuild tree.

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

Non-merge commits (relative to Linus' tree): 12041
 12243 files changed, 686052 insertions(+), 250965 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 431 trees (counting Linus' and 135 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-10-02 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 11:33 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-01  4:43 Stephen Rothwell
2021-10-01  7:09 Stephen Rothwell
2020-10-01 11:39 Stephen Rothwell
2019-10-01  2:13 Stephen Rothwell
2015-10-01  6:50 Stephen Rothwell
2014-10-01  7:54 Stephen Rothwell
2014-10-02  3:59 ` Guenter Roeck
2013-10-01 11:03 Thierry Reding
2012-10-01 15:03 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=ar-WbnTc3mEdbz9C@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

all inboxes | Powered by JetHome®