linux-kernel - linux-next: manual merge of the jc_docs tree with the mm-nomm-stable tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <aXeZQy24nAzwEKF3@sirena.org.uk>
Date: Mon, 26 Jan 2026 16:41:39 +0000
From: Mark <broonie@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	Jani Nikula <jani.nikula@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Mike Rapoport <rppt@...nel.org>
Subject: linux-next: manual merge of the jc_docs tree with the mm-nomm-stable
 tree

Hi all,

Today's linux-next merge of the jc_docs tree got a conflict in:

  Documentation/core-api/kho/index.rst

between commit:

  35c554410d81c ("kho: docs: combine concepts and FDT documentation")

from the mm-nomm-stable tree and commit:

  a592a36e49372 ("Documentation: use a source-read extension for the index link boilerplate")

from the jc_docs tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc Documentation/core-api/kho/index.rst
index dcc6a36cc134c,51ea41c6a20d5..0000000000000
--- a/Documentation/core-api/kho/index.rst
+++ b/Documentation/core-api/kho/index.rst

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)