[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200617104612.59695467@canb.auug.org.au>
Date: Wed, 17 Jun 2020 10:46:12 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Daniel Vetter <daniel.vetter@...ll.ch>,
Intel Graphics <intel-gfx@...ts.freedesktop.org>,
DRI <dri-devel@...ts.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Ben Skeggs <bskeggs@...hat.com>,
Emil Velikov <emil.velikov@...labora.com>
Subject: linux-next: manual merge of the drm-misc tree with Linus' tree
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/nouveau/nouveau_display.c
between commit:
183405879255 ("drm/nouveau/kms: Remove field nvbo from struct nouveau_framebuffer")
from Linus' tree and commit:
cdc194cebd71 ("drm/nouveau: remove _unlocked suffix in drm_gem_object_put_unlocked")
from the drm-misc tree.
I fixed it up (the former just removed one of the functions modified
by the latter) 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
Powered by blists - more mailing lists