linux-kernel - linux-next: manual merge of the omap 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20190917115200.GD3524@sirena.co.uk>
Date:   Tue, 17 Sep 2019 12:52:00 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Tony Lindgren <tony@...mide.com>
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 omap tree with Linus' tree

Hi all,

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

  arch/arm/mach-omap2/Makefile

between commit:

  3846a3b9511c51 ("ommu/omap: fix boot issue on remoteprocs with AMMU/Unicache")

from Linus' tree and commit:

  0a55bff7003967 ("Trivial merge conflict between omap and iommu branches.")

from the omap tree.

I fixed it up (see below, dropping the OMAP change) 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 arch/arm/mach-omap2/Makefile
index 8f208197988fe,8253112a4e51e..0000000000000
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile

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