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.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=unavailable 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 1C129C282DB for ; Sat, 2 Feb 2019 10:12:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D5D99218A6 for ; Sat, 2 Feb 2019 10:12:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549102375; bh=V67/DR7kBa7CON0ew0ooSzTXzjEuFwcNUbYDLjGH7dc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Tq+1wxoWDtVWBUM3CYLq+nkKxHzrHTEIjqV/Hhz5Kw3/AjRNbvA9YvrQf1JEdZ/Al WCo9wNZIPw0P4mG/kQGsLWY/SrrqKVA+FpSPdV+a64mEQ+H3F+fT2KZqEfdD9GeTTR 1Kz6qIfIqaoPQf6wmXDIZe3VK1Ae0DOVEVZnPvss= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727746AbfBBKMw (ORCPT ); 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 ); 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 To: Christoph Hellwig Cc: John Crispin , Dmitry Tarnyagin , Nicolas Ferre , Sudip Mukherjee , Felipe Balbi , 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: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@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