From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 40TK5m16SMzDrDT for ; Sun, 22 Apr 2018 16:13:01 +1000 (AEST) Date: Sun, 22 Apr 2018 11:47:33 +0530 From: Vinod Koul To: Wolfram Sang Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, kernel-janitors@vger.kernel.org, Ludovic Desroches , Dan Williams , Li Yang , Zhang Wei , Linus Walleij , linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH 07/61] dma: simplify getting .drvdata Message-ID: <20180422061733.GU6014@localhost> References: <20180419140641.27926-1-wsa+renesas@sang-engineering.com> <20180419140641.27926-8-wsa+renesas@sang-engineering.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180419140641.27926-8-wsa+renesas@sang-engineering.com> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Apr 19, 2018 at 04:05:37PM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. Do you mind splitting this per driver please, that makes it easy to manage for me :) -- ~Vinod