public inbox for linux-next@vger.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 Jan 30
Date: Fri, 30 Jan 2026 18:52:36 +0000	[thread overview]
Message-ID: <aXz99P76SX65G2CT@sirena.org.uk> (raw)

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

Hi all,

I have an added an arm64 allnoconfig intermediate build.

Changes since 20260129:

The keys-next tree was added.

The drm tree acquired multiple conflicts with the drm-fixes tree.

The mtd tree acquired a build failure, I have used the version from
20260129 instead.

The drm-xe tree acquired a conflict with the drm-fixes tree.

The keys-next tree acquired a conflict with the modules tree.

Non-merge commits (relative to Linus' tree): 9978
 9682 files changed, 563559 insertions(+), 207870 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 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. And finally, a
simple boot test of the powerpc pseries_le_defconfig kernel in qemu
(with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 405 trees (counting Linus' and 121 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-01-30 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 18:52 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-30  3:10 linux-next: Tree for Jan 30 Stephen Rothwell
2024-01-30  2:58 Stephen Rothwell
2023-01-30  5:54 Stephen Rothwell
2020-01-30  4:28 Stephen Rothwell
2019-01-30  7:39 Stephen Rothwell
2018-01-30  5:26 Stephen Rothwell
2017-01-30  6:49 Stephen Rothwell
2017-01-30  6:49 ` Stephen Rothwell
2015-01-30  7:02 Stephen Rothwell
2014-01-30  4:11 Stephen Rothwell
2012-01-30  3:41 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=aXz99P76SX65G2CT@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