Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp1517738ima;
        Sat, 2 Feb 2019 02:16:25 -0800 (PST)
X-Google-Smtp-Source: AHgI3IZgDDWRdqcInKMyRuj2yAbONK0sxUxDwXege/t786pzgUC881LgxcPdc6OJ/O0JiEj6hebP
X-Received: by 2002:a17:902:7c8a:: with SMTP id y10mr862328pll.71.1549102585845;
        Sat, 02 Feb 2019 02:16:25 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1549102585; cv=none;
        d=google.com; s=arc-20160816;
        b=DtKAehGD3X+4yUTfe2m5NK/9veLbIv3Ub/JMoVpGxkHL9rNqw+iGx0XJxCLhLVQ6Sq
         1NGnGwkWc+S3fnfrUuy7aFTEwNFB5WlVGeqo0Q91TeuoiKiWmw3H1ieC1yZPNE4Z+/Pv
         rlpHtOnF06qR2R1/YYkqkqquKhGimLbmHMIiewNjpF1K5lrG3kw6dhTTVl6OSa0M1+VM
         vJEUY9cD3qr1QysWEdr2z3xkS4KfQonu1v79Ojrepvu1ye5W/h0Cua1HHNJyem4SsVdT
         Wd7p8ydsafxo0dlHxhNiiw8xOYFjaVf0+Ky0y0+lJkZFCI4HZcZHjT8VMHc42VK3Awb6
         vKDQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:user-agent:in-reply-to
         :content-disposition:mime-version:references:message-id:subject:cc
         :to:from:date:dkim-signature;
        bh=epR8IagQbLwjt+9lCIV1bNnKO4JPn1cC5cpLiYY8y54=;
        b=Uc6VJZASQGXmlGCddpQdMv2YrVF63+geYEO75hPKQTl5RPxwE3VFpKUuWRz2KhsaNG
         MjqO/1MTxrVknuOz1FOpdQ3BD/duecLOSTuWe1m4rPBcNunDhNs2NHdrptwdP+vojI3V
         /1SP898YJ0VMvy3VtMtS6hnT58s0VKN+bVuAX5inmTK/fAxJSFDbpd9+vg4gPg1CEoKQ
         dUCdXkTIn/jkyWATRvwMwtxqQDxYvsaR+iTWP6xzPL7+YSBFhVMCfaSSeMFKQTq/XnAZ
         Glh9BUDGX9wNaqY0HzjB/SeEOD5tEZsQCUjwlX5vrweKevc5Rf90SyPejbUUp9Op8vfm
         5pzw==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@kernel.org header.s=default header.b=LPuV6ltu;
       spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id m5si10199844pfm.149.2019.02.02.02.16.10;
        Sat, 02 Feb 2019 02:16:25 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@kernel.org header.s=default header.b=LPuV6ltu;
       spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1727719AbfBBKMw (ORCPT <rfc822;chenhe.dev@gmail.com>
        + 99 others); Sat, 2 Feb 2019 05:12:52 -0500
Received: from mail.kernel.org ([198.145.29.99]:35670 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726255AbfBBKMw (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 2 Feb 2019 05:12:52 -0500
Received: from localhost (unknown [125.16.100.118])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id 861E820870;
        Sat,  2 Feb 2019 10:12:50 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1549102371;
        bh=V67/DR7kBa7CON0ew0ooSzTXzjEuFwcNUbYDLjGH7dc=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=LPuV6ltu4Lj3zjCnvwB/17WBfxQjIFVGDAu6GC749dxKfkvO8+cNTekE24McxIAbe
         kIoUExnO86UuM3MxpnaSUbINeNw31OkgT5NeYVQ8wRVeSfNNj9WVu080T4jznw0N+Z
         H53omImB0vvYnZ47dLdCzrPlcETPo8cTdIzRs6n0=
Date:   Sat, 2 Feb 2019 15:41:21 +0530
From:   Vinod Koul <vkoul@kernel.org>
To:     Christoph Hellwig <hch@lst.de>
Cc:     John Crispin <john@phrozen.org>,
        Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
        Nicolas Ferre <nicolas.ferre@microchip.com>,
        Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
        Felipe Balbi <balbi@kernel.org>, linux-mips@vger.kernel.org,
        linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
        netdev@vger.kernel.org, linux-usb@vger.kernel.org,
        linux-fbdev@vger.kernel.org, alsa-devel@alsa-project.org,
        iommu@lists.linux-foundation.org
Subject: Re: [PATCH 02/18] dmaengine: imx-sdma: pass struct device to DMA API
 functions
Message-ID: <20190202101121.GE4296@vkoul-mobl>
References: <20190201084801.10983-1-hch@lst.de>
 <20190201084801.10983-3-hch@lst.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190201084801.10983-3-hch@lst.de>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 01-02-19, 09:47, Christoph Hellwig wrote:
> The DMA API generally relies on a struct device to work properly, and
> only barely works without one for legacy reasons.  Pass the easily
> available struct device from the platform_device to remedy this.

This looks good to me but fails to apply. Can you please base it on
dmaengine-next or linux-next please and resend

Thanks
-- 
~Vinod