Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753466AbcCVXlD (ORCPT ); Tue, 22 Mar 2016 19:41:03 -0400 Received: from mail-vk0-f45.google.com ([209.85.213.45]:35251 "EHLO mail-vk0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751280AbcCVXlA (ORCPT ); Tue, 22 Mar 2016 19:41:00 -0400 MIME-Version: 1.0 In-Reply-To: <56F1D33A.9050509@redhat.com> References: <1458686031-31031-1-git-send-email-moritz.fischer@ettus.com> <56F1CC7B.7040909@redhat.com> <56F1D33A.9050509@redhat.com> Date: Tue, 22 Mar 2016 16:40:59 -0700 Message-ID: Subject: Re: [RFC 0/2] staging: ion: of_ion_device_get From: Moritz Fischer To: Laura Abbott Cc: Arnd Bergmann , Greg KH , arve@android.com, riandrews@android.com, Sumit Semwal , dan.carpenter@oracle.com, sriram@marirs.net.in, Linux Kernel Mailing List , devel@driverdev.osuosl.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 411 Lines: 13 On Tue, Mar 22, 2016 at 4:20 PM, Laura Abbott wrote: > If allocation is coming from userspace and drivers are only importing > you should be using the dma_buf APIs instead of Ion APIs directly. > Ion is a dma_buf exporter and dma_buf APIs are the preferred API. Ok, thanks. Sounds reasonable. Thanks, Moritz PS: My email skills today suck ... sorry about that ... I should go home ...