From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751962AbdLNFOB (ORCPT ); Thu, 14 Dec 2017 00:14:01 -0500 Received: from mga05.intel.com ([192.55.52.43]:4975 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751587AbdLNFNz (ORCPT ); Thu, 14 Dec 2017 00:13:55 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,399,1508828400"; d="scan'208";a="2671713" Date: Thu, 14 Dec 2017 10:47:39 +0530 From: Vinod Koul To: Mark Brown , Takashi Iwai Cc: Greg Kroah-Hartman , Mark Rutland , devicetree@vger.kernel.org, alsa-devel@alsa-project.org, Jonathan Corbet , linux-arm-msm@vger.kernel.org, linux-doc@vger.kernel.org, j.neuschaefer@gmx.net, linux-kernel@vger.kernel.org, Rob Herring , srinivas.kandagatla@linaro.org, pombredanne@nexb.com, sdharia@codeaurora.org Subject: Re: [alsa-devel] [PATCH v10 08/13] regmap: add SLIMbus support Message-ID: <20171214051739.GV18649@localhost> References: <20171211234307.14465-1-srinivas.kandagatla@linaro.org> <20171211234307.14465-9-srinivas.kandagatla@linaro.org> <20171213092537.GB12631@kroah.com> <20171213160611.GO6416@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171213160611.GO6416@sirena.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 13, 2017 at 04:06:11PM +0000, Mark Brown wrote: > > On Mon, Dec 11, 2017 at 11:43:02PM +0000, srinivas.kandagatla@linaro.org wrote: > > > Mark, can I get an Ack for this patch so I can take it through my tree > > with the other patches in this series? > > I'm actually not seeing a direct dependency here (there's a depends in > place stopping the regmap code building if the Slimbus core isn't > enabled) so if you want you can go ahead and apply the main stuff and I > can apply the regmap change separately, it'll avoid Makefile/Kconfig > conflicts anyway. + Takashi FWIW, since this is another MIPI Audio specfic bus, would it make sense for this series to go thru sound/ tree? I have discussed with Takashi and Greg for soundwire and we are taking sound path. Would that be okay here too? Either ways I dont mind :) Thanks -- ~Vinod