Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35;
Date:   Wed, 22 Nov 2023 11:51:37 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Daniel Vetter <daniel.vetter@ffwll.ch>,
        Jani Nikula <jani.nikula@linux.intel.com>,
        Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc:     Intel Graphics <intel-gfx@lists.freedesktop.org>,
        DRI <dri-devel@lists.freedesktop.org>,
        Alex Deucher <alexander.deucher@amd.com>,
        Imre Deak <imre.deak@intel.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        Wayne Lin <Wayne.Lin@amd.com>
Subject: linux-next: manual merge of the drm-intel tree with Linus' tree
Message-ID: <20231122115137.04a33a6c@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/I2H4f6VqQn9wBne0MzTm_OF";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/I2H4f6VqQn9wBne0MzTm_OF
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

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

  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_helpers.c

between commit:

  9031e0013f81 ("drm/amd/display: Fix mst hub unplug warning")

from Linus' tree and commit:

  191dc43935d1 ("drm/dp_mst: Store the MST PBN divider value in fixed point=
 format")

from the drm-intel tree.

I fixed it up (I just used the former) 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

--Sig_/I2H4f6VqQn9wBne0MzTm_OF
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmVdUJkACgkQAVBC80lX
0GzV1wf9Gz35ouxAlzrIOa/+NQj7wvVFopvSvxFv+GEE8UCRSrnkbg96TFLa+4of
vlG5Bvbtmd0N9OoNKGminwK3T5ghQNa38oZ9Ic1tSXEcJY+5W5XuN+PqFRU2eupv
8owuRqF2dH424CfbV0EE5FEr5hDJWNY6e3hFl+hUcH/CF9Z9UYImw51LZxSQyF4d
LhDqVlKq0bgBID6zDTWMRzRB188rdVN+EGjxz+xsO5ysPh7OLLdMdZL5RbcpfE0F
uUVvCDb9ksqZ5HElFgz5sEiYmOVv9ba1u93TtuPrIzLiF69x7VHqhH7cTSOJ9ODJ
g50onkxt3YOqEiasXkAqBMlhGbOCGQ==
=W9Ap
-----END PGP SIGNATURE-----

--Sig_/I2H4f6VqQn9wBne0MzTm_OF--