linux-kernel - linux-next: manual merge of the mips tree with Linus' 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: <20190918113323.GD2596@sirena.co.uk>
Date:   Wed, 18 Sep 2019 12:33:23 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Ralf Baechle <ralf@...ux-mips.org>, James Hogan <jhogan@...nel.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: manual merge of the mips tree with Linus' tree

Hi all,

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

  Documentation/index.rst

between several commits from Linus' tree and commit:

  97689a1a3fdad101d ("doc: Add doc for the Ingenic TCU hardware")

from the mips 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/index.rst
index b5fd87e7dbee4,87214feda41fb..0000000000000
--- a/Documentation/index.rst
+++ b/Documentation/index.rst

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