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  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:   Fri, 1 May 2020 13:45:36 +1000
From:   Stephen Rothwell <>
To:     Dave Airlie <>,
        Daniel Vetter <>,
        Intel Graphics <>,
        DRI <>
Cc:     Linux Next Mailing List <>,
        Linux Kernel Mailing List <>,
        Randy Dunlap <>,
        Sumit Semwal <>,
        Christian K├Ânig <>
Subject: linux-next: manual merge of the drm tree with the drm-misc-fixes

Hi all,

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


between commit:

  6f49c2515e22 ("dma-buf: fix documentation build warnings")

from the drm-misc-fixes tree and commit:

  09606b5446c2 ("dma-buf: add peer2peer flag")

from the drm 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.

Stephen Rothwell

diff --cc include/linux/dma-buf.h
index 57bcef6f988a,82e0a4a64601..000000000000
--- a/include/linux/dma-buf.h
+++ b/include/linux/dma-buf.h
@@@ -333,8 -334,16 +333,16 @@@ struct dma_buf 
   * Attachment operations implemented by the importer.
  struct dma_buf_attach_ops {
+ 	/**
+ 	 * @allow_peer2peer:
+ 	 *
+ 	 * If this is set to true the importer must be able to handle peer
+ 	 * resources without struct pages.
+ 	 */
+ 	bool allow_peer2peer;
 -	 * @move_notify
 +	 * @move_notify: [optional] notification that the DMA-buf is moving
  	 * If this callback is provided the framework can avoid pinning the
  	 * backing store while mappings exists.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists