linux-kernel - linux-next: manual merge of the phy-next tree with the gcom 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]

Date:   Tue, 26 Oct 2021 15:44:15 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Kishon Vijay Abraham I <kishon@...com>,
        Vinod Koul <vkoul@...nel.org>, Andy Gross <agross@...nel.org>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Shawn Guo <shawn.guo@...aro.org>,
        Stephan Gerhold <stephan@...hold.net>
Subject: linux-next: manual merge of the phy-next tree with the gcom tree

Hi all,

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

  arch/arm64/boot/dts/qcom/apq8096-db820c.dtsi

between commit:

  442ee1fc60c4 ("arm64: dts: qcom: Drop unneeded extra device-specific includes")

from the gcom tree and commit:

  956bbf2a94e8 ("arm64: dts: qcom: Add missing vdd-supply for QUSB2 PHY")

from the phy-next tree.

I fixed it up (the former removed the file, so I did that) 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

Content of type "application/pgp-signature" skipped