linux-kernel - linux-next: manual merge of the etnaviv tree with the drm-misc 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:   Mon, 26 Nov 2018 13:58:06 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Lucas Stach <l.stach@...gutronix.de>,
        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>,
        Fernando Ramos <greenfoo@...egarage.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Thomas Zimmermann <tzimmermann@...e.de>
Subject: linux-next: manual merge of the etnaviv tree with the drm-misc tree

Hi Lucas,

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

  drivers/gpu/drm/etnaviv/etnaviv_drv.c

between commit:

  808bad32ea42 ("drm: replace "drm_dev_unref" function with "drm_dev_put"")

from the drm-misc tree and commit:

  99e294492ef9 ("drm/etnaviv: Replace drm_dev_unref with drm_dev_put")

from the etnaviv tree.

I fixed it up (I used the latter which also renamed a label
appropriatedly) 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