From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932648AbbJACH5 (ORCPT ); Wed, 30 Sep 2015 22:07:57 -0400 Received: from mga11.intel.com ([192.55.52.93]:47316 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750940AbbJACH4 (ORCPT ); Wed, 30 Sep 2015 22:07:56 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,615,1437462000"; d="scan'208";a="816734805" Date: Thu, 1 Oct 2015 07:40:48 +0530 From: Vinod Koul To: Kuninori Morimoto Cc: Linux-ALSA , Simon , linux-kernel@vger.kernel.org, Liam Girdwood , Mark Brown , dmaengine@vger.kernel.org, Dan Williams Subject: Re: [alsa-devel] [PATCH 1/2] dmaengine: OF DMAEngine API based on CONFIG_DMA_OF instead of CONFIG_OF Message-ID: <20151001021048.GD11757@localhost> References: <87wpwpurzk.wl%kuninori.morimoto.gx@renesas.com> <20150821082636.GK13546@localhost> <87d1yglvcy.wl%kuninori.morimoto.gx@renesas.com> <87bne0lvbe.wl%kuninori.morimoto.gx@renesas.com> <20150824091838.GH13546@localhost> <87si786xc6.wl%kuninori.morimoto.gx@renesas.com> <87zj0ulm4z.wl%kuninori.morimoto.gx@renesas.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87zj0ulm4z.wl%kuninori.morimoto.gx@renesas.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 10, 2015 at 08:26:11AM +0000, Kuninori Morimoto wrote: > Hi Vinod > > > > > 5fa422c ("dmaengine: move drivers/of/dma.c -> drivers/dma/of-dma.c") > > > > moved OF base DMAEngine code to of-dma.c, then it based on CONFIG_DMA_OF. > > > > But, OF base DMAEngine API on of_dma.h still based on CONFIG_OF now. > > > > So, current kernel can't find OF base DMAEngine API if .config has CONFIG_OF, > > > > but not have CONFIG_DMA_OF. This patch tidyup it. > > > > > > I did a quick build with arm config, but didn't see any failures. But still > > > am worried about random config and other builds may find. > > > > > > So I think it would be safer to merge this patch after merge window so that > > > we have ample time to fix any issue > > Which branch can I find this patch ? Sorry I missed to do this after merge window. Applied now -- ~Vinod