linux-kernel - linux-next: manual merge of the amlogic tree with the arm-soc 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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160920101938.5d46a0ab@canb.auug.org.au>
Date:   Tue, 20 Sep 2016 10:19:38 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Kevin Hilman <khilman@...libre.com>,
        Carlo Caione <carlo@...one.org>,
        Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
        ARM <linux-arm-kernel@...ts.infradead.org>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Jerome Brunet <jbrunet@...libre.com>
Subject: linux-next: manual merge of the amlogic tree with the arm-soc tree

Hi all,

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

  arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi

between commit:

  8735053d7968 ("ARM64: dts: meson-gxbb-p20x: Enable USB Nodes")

from the arm-soc tree and commit:

  d82801a385a1 ("ARM64: dts: meson-gxbb-p20x: Enable USB Nodes")

from the amlogic tree.

This patch was modified before being merged into the arm-soc tree.
Please clean up the amlogic tree.

I fixed it up (I used the arm-soc tree version) 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.

-- 
Cheers,
Stephen Rothwell