[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa1c5b2f-fa90-4390-edc6-33b87fab5e09@android.com>
Date:   Mon, 7 Oct 2019 09:50:31 -0700
From:   Mark Salyzyn <salyzyn@...roid.com>
To:     Christoph Hellwig <hch@....de>,
        Catalin Marinas <catalin.marinas@....com>
Cc:     linux-kernel@...r.kernel.org, kernel-team@...roid.com,
        Andrew Morton <akpm@...ux-foundation.org>,
        Yue Hu <huyue2@...ong.com>, Mike Rapoport <rppt@...ux.ibm.com>,
        Will Deacon <will@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ryohei Suzuki <ryh.szk.cmnty@...il.com>,
        Doug Berger <opendmb@...il.com>,
        Andrey Konovalov <andreyknvl@...gle.com>,
        Peng Fan <peng.fan@....com>, linux-mm@...ck.org,
        Robin Murphy <robin.murphy@....com>
Subject: Re: [PATCH] mm: export cma alloc and release
On 10/5/19 1:37 AM, Christoph Hellwig wrote:
> On Thu, Oct 03, 2019 at 09:55:28AM +0100, Catalin Marinas wrote:
>> Aren't drivers supposed to use the DMA API for such allocations rather
>> than invoking cma_*() directly?
> Yes, they are.
We have an engineer assigned to rewriting the ion memory driver to use 
dma_buf interfaces. Hopefully that effort will solve the problem of 
requiring these interfaces to be exported so that that driver (and 
others) can be modularized.
Thanks for the reviews, drop this patch from the list and we will 
regroup, and accept that standing code in the kernel can not be 
modularized for the moment.
Sincerely -- Mark Salyzyn
Powered by blists - more mailing lists
 
