From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: linux-next: manual merge of the drm-misc tree with the amdgpu tree Date: Wed, 12 Jun 2019 11:46:15 +1000 Message-ID: <20190612114615.69a78655@canb.auug.org.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2063793286==" Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Daniel Vetter , Intel Graphics , DRI , Alex Deucher Cc: Dave Airlie , Charlene Liu , Linux Next Mailing List , Sam Ravnborg , Linux Kernel Mailing List List-Id: dri-devel@lists.freedesktop.org --===============2063793286== Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/4P5AwUEph_+1clfAOt0GSyc"; protocol="application/pgp-signature" --Sig_/4P5AwUEph_+1clfAOt0GSyc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/amd/display/dc/dce/dce_audio.c between commit: c7c7192c56d2 ("drm/amd/display: add audio related regs") from the amdgpu tree and commit: 4fc4dca8320e ("drm/amd: drop use of drmp.h in os_types.h") from the drm-misc 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. --=20 Cheers, Stephen Rothwell diff --cc drivers/gpu/drm/amd/display/dc/dce/dce_audio.c index d43d5d924c19,9b078a71de2e..000000000000 --- a/drivers/gpu/drm/amd/display/dc/dce/dce_audio.c +++ b/drivers/gpu/drm/amd/display/dc/dce/dce_audio.c @@@ -22,7 -22,9 +22,10 @@@ * Authors: AMD * */ +=20 + #include +=20 +#include "../dc.h" #include "reg_helper.h" #include "dce_audio.h" #include "dce/dce_11_0_d.h" --Sig_/4P5AwUEph_+1clfAOt0GSyc Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl0AWWgACgkQAVBC80lX 0GyInAf9EkndAclA4v6jGiJ3ikxT3HRWH+0v8pKJ0AH0Q2+KPoLfPRfVMdOWEAbb 2L6jAiiPL2a2RCFSnsFMbxP6Ki48DQiJM2lhw/VA54Y8Db1XGXmN+0pmGCE1dvbc 0Bksmtcn/Hek8uE7GmM4ZfTLW8vnca7aey+KqC8bFt3oYntotcA2wYq5k0b8zuXV vFZzj12lS5+N+f41zoYVBLwaHKB7h9mdwcQlPFRAl5YTySnXXieR2TL4h3Vzs16E vtohgcJWUqiJSkAFwahAyW43Zt18BdD3kmgZqSpv0JgkWxXhrcTbUvSnbSTiRUmX YaxywF9MrIjMLwZzCG3GT1Knbeph/w== =dUfW -----END PGP SIGNATURE----- --Sig_/4P5AwUEph_+1clfAOt0GSyc-- --===============2063793286== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============2063793286==--