On Sun, Mar 18, 2012 at 11:34 PM, Daniel Vetter
wrote:
> Otherwise subsystems will get this wrong and end up with and second
> export ioctl with the flag and O_CLOEXEC support added.
Its not actually dma_buf_export that takes the O_CLOEXEC flag its dma_buf_fd
I'm not sure how blindly we should
On Sun, Mar 18, 2012 at 11:34 PM, Daniel Vetter wrote:
> Otherwise subsystems will get this wrong and end up with and second
> export ioctl with the flag and O_CLOEXEC support added.
Its not actually dma_buf_export that takes the O_CLOEXEC flag its dma_buf_fd
I'm not sure how blindly we should b
Otherwise subsystems will get this wrong and end up with and second
export ioctl with the flag and O_CLOEXEC support added.
Signed-Off-by: Daniel Vetter
---
Documentation/dma-buf-sharing.txt |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Documentation/dma-buf-sharin
Otherwise subsystems will get this wrong and end up with and second
export ioctl with the flag and O_CLOEXEC support added.
Signed-Off-by: Daniel Vetter
---
Documentation/dma-buf-sharing.txt |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Documentation/dma-buf-sharin