linux-kernel - Re: [PATCH v3 0/7] ARM/ASoC: OMAP3: Fix McBSP2/3 sidetone support

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] [day] [month] [year] [list]

Message-ID: <f7af7b30-563a-0048-9696-6ad0125d8f68@ti.com>
Date:	Fri, 13 May 2016 14:45:34 +0300
From:	Peter Ujfalusi <peter.ujfalusi@...com>
To:	Tony Lindgren <tony@...mide.com>
CC:	<jarkko.nikula@...mer.com>, <paul@...an.com>,
	<lgirdwood@...il.com>, <broonie@...nel.org>, <t-kristo@...com>,
	<linux-omap@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<alsa-devel@...a-project.org>
Subject: Re: [PATCH v3 0/7] ARM/ASoC: OMAP3: Fix McBSP2/3 sidetone support

On 05/12/16 19:42, Tony Lindgren wrote:
> * Peter Ujfalusi <peter.ujfalusi@...com> [160511 01:46]:
>> Tony, Paul,
>>
>> On 04/29/16 13:53, Peter Ujfalusi wrote:
>>> Hi,
>>>
>>> Based on the ongoing discussion on v2 (ARM: OMAP3: Fix McBSP2/3 hwmod setup for
>>> sidetone) I have dropped the removal of the sidetone hwmod and only corrected
>>> it. The series now includes all related changes needed to have correct sidetone
>>> support whenever we boot in legacy or in DT mode.
>>>
>>> This time the ASoC part have dependency on earlier patches so they can not be
>>> applied separately.
>>
>> How should we proceed from here? I don't want to start designing the ST
>> separation infrastructure which would be based on this series, but if there
>> are outstanding issues found on this, I would need to go back to the drawing
>> board.
>> The separation will be mostly new code and code shuffle in ASoC, but for
>> legacy I will need to build up something in arch as well, so I would need at
>> least one release cycle to start with things.
> 
> Well looks like we have all the acks, so I can apply these. We have
> not heard from Paul on this for a while, so let's wait few days for
> that.
> 
> Meanwhile, Mark wanted to fix the subject for one of the patches, care
> to repost that at least? Or the whole series with acks, could be a
> pull request too against v4.6-rc1 :)

Thanks, I'll wait for couple of days for Paul to review and I will prepare v4
and a pull request.

-- 
Péter