From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BB47AC4740A for ; Sat, 5 Oct 2019 08:38:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9C333222C9 for ; Sat, 5 Oct 2019 08:38:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727411AbfJEIiB (ORCPT ); Sat, 5 Oct 2019 04:38:01 -0400 Received: from verein.lst.de ([213.95.11.211]:49353 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725927AbfJEIiA (ORCPT ); Sat, 5 Oct 2019 04:38:00 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 1994E68B05; Sat, 5 Oct 2019 10:37:54 +0200 (CEST) Date: Sat, 5 Oct 2019 10:37:53 +0200 From: Christoph Hellwig To: Catalin Marinas Cc: Mark Salyzyn , linux-kernel@vger.kernel.org, kernel-team@android.com, Andrew Morton , Yue Hu , Mike Rapoport , Will Deacon , Thomas Gleixner , Ryohei Suzuki , Doug Berger , Andrey Konovalov , Peng Fan , linux-mm@kvack.org, Christoph Hellwig , Robin Murphy Subject: Re: [PATCH] mm: export cma alloc and release Message-ID: <20191005083753.GA14691@lst.de> References: <20191002212257.196849-1-salyzyn@android.com> <20191003085528.GB21629@arrakis.emea.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191003085528.GB21629@arrakis.emea.arm.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.