lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <682e689d-d196-fe38-fc6f-e51a981ee18e@linaro.org>
Date:   Thu, 14 Dec 2017 13:16:13 +0000
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Takashi Iwai <tiwai@...e.de>, Vinod Koul <vinod.koul@...el.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Mark Rutland <mark.rutland@....com>,
        devicetree@...r.kernel.org, alsa-devel@...a-project.org,
        Jonathan Corbet <corbet@....net>,
        linux-arm-msm@...r.kernel.org, linux-doc@...r.kernel.org,
        j.neuschaefer@....net, linux-kernel@...r.kernel.org,
        Rob Herring <robh+dt@...nel.org>, pombredanne@...b.com,
        sdharia@...eaurora.org
Subject: Re: [alsa-devel] [PATCH v10 08/13] regmap: add SLIMbus support



On 14/12/17 08:19, Takashi Iwai wrote:
> On Thu, 14 Dec 2017 06:17:39 +0100,
> Vinod Koul wrote:
>>
>> 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@...aro.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 :)
> 
> Me too, I don't mind who takes what.
> Just let me know.
> 

It was implied early that Greg would pick up the main stuff and Mark can 
apply regmap separately to avoid Makefile/Kconfig conflicts.

Lets keep it that way to avoid anymore confusion.

Thanks,
srini


> 
> thanks,
> 
> Takashi
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ