linux-kernel - Re: [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories

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]

Date:   Sun, 11 Nov 2018 18:37:40 +0200
From:   Jarkko Nikula <jarkko.nikula@...mer.com>
To:     Peter Ujfalusi <peter.ujfalusi@...com>,
        Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>, tony@...mide.com,
        nsekhar@...com
Cc:     alsa-devel@...a-project.org, linux-omap@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        jsarha@...com
Subject: Re: [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories

On 11/8/18 10:37 AM, Peter Ujfalusi wrote:
> The series also includes patches to updated the arch/arm/ files (defconfigs,
> source files using audio Kconfig symbols).
> 
> I believe with v1 all of this can be merged via ASoC tree as the chances of
> conflicts are low for the touched arch/arm files. But Sekhar and Tony can
> correct me if I'm wrong.
> 
> I think I have catched all (I hope) issues regarding to Kconfig thanks to the
> various autobuild machines out there kindly testing my linux-next-wip branch.
> 
> I would appreciate any testing comments before I send the v1!
> 
I applied on top of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git commit
abd97b7c53ac ("Merge branch 'asoc-4.21' into asoc-next").

Patches 2 and 6 didn't apply and 7-8 I skipped. For my functional
testing none of those were required.

For the sound/soc/{omap => ti} conversion you may add:

Tested-by: Jarkko Nikula <jarkko.nikula@...mer.com>
Acked-by: Jarkko Nikula <jarkko.nikula@...mer.com>