public inbox for linux-kernel@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 Oct 17
Date: Fri, 17 Oct 2025 16:11:56 +0100	[thread overview]
Message-ID: <aPJcvDHsHD-Wdy30@sirena.org.uk> (raw)

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

Hi all,

Stephen will be back from vaction on Monday so normal service will be
resumed.

Changes since 20251016:

The mm-nomm-unstable tree gained a build failure for which I reverted a
commit.

The libcrypto tree gained a conflict with the crypto tree.

The gpio-brgl tree gained a build failure, I used the version from
20251016 instead.

Non-merge commits (relative to Linus' tree): 2117
 2125 files changed, 70693 insertions(+), 31577 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 an arm64
defconfig, an allmodconfig for x86_64, a multi_v7_defconfig for arm 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,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and
pseries_le_defconfig and i386, arm64, 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 407 trees (counting Linus' and 406 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 Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

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

             reply	other threads:[~2025-10-17 15:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 15:11 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17  8:55 linux-next: Tree for Oct 17 Stephen Rothwell
2023-10-17  4:12 Stephen Rothwell
2022-10-17  1:22 Stephen Rothwell
2019-10-17  4:26 Stephen Rothwell
2018-10-17  6:06 Stephen Rothwell
2016-10-17  2:09 Stephen Rothwell
2014-10-17  3:34 Stephen Rothwell
2013-10-18  0:38 Mark Brown
2013-10-18  7:45 ` Olof Johansson
2013-10-18  8:22   ` Thierry Reding
2013-10-18 16:22     ` Kevin Hilman
2013-10-18 17:01       ` Kevin Hilman
2013-10-18 17:55       ` Olof Johansson
2013-10-18 11:33   ` Guenter Roeck
2012-10-17  2:43 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=aPJcvDHsHD-Wdy30@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