linux-kernel - linux-next: manual merge of the drm tree with the jc

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>] [day] [month] [year] [list]

Date:   Mon, 12 Dec 2016 11:57:53 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Dave Airlie <airlied@...ux.ie>, Jonathan Corbet <corbet@....net>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        SeongJae Park <sj38.park@...il.com>
Subject: linux-next: manual merge of the drm tree with the jc_docs tree

Hi Dave,

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

  Documentation/driver-api/infrastructure.rst

between commits:

  3080b056b3d4 ("docs/driver-api: Apply changed source file names")
  868c97a846a7 ("dma-buf: Extract dma-buf.rst")

from the jc_docs tree and commit:

  8a5846bf5d47 ("doc/dma-buf: Fix up include directives")

from the drm tree.

I fixed it up (the text modified by the latter was also modified by
commit 3080b056b3d4, then 868c97a846a7 moved it all to another file) 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