linux-kernel - Re: [PATCH v4 0/2] ASoC: da7219: Convert driver to use generic FW functions

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:	Wed, 22 Jun 2016 03:05:26 +0200
From:	"Rafael J. Wysocki" <rafael@...nel.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	"Opensource [Adam Thomson]" <Adam.Thomson.Opensource@...semi.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Robert Moore <robert.moore@...el.com>,
	Lv Zheng <lv.zheng@...el.com>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	Len Brown <lenb@...nel.org>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Rob Herring <robh+dt@...nel.org>,
	Frank Rowand <frowand.list@...il.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	devicetree <devicetree@...r.kernel.org>,
	alsa-devel <alsa-devel@...a-project.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Support Opensource <Support.Opensource@...semi.com>,
	Sathyanarayana Nujella <sathyanarayana.nujella@...el.com>
Subject: Re: [PATCH v4 0/2] ASoC: da7219: Convert driver to use generic FW functions

On Wed, Jun 22, 2016 at 1:21 AM, Mark Brown <broonie@...nel.org> wrote:
> On Tue, Jun 21, 2016 at 10:54:39PM +0000, Opensource [Adam Thomson] wrote:
>> On 21 June 2016 23:30, Rafael J. Wysocki wrote:
>
>> > I'm fine with the first patch and the second one carries a couple of
>> > ACKs already, so do you want me to apply them both?
>
> None of whom are from anyone who works on the subsystem at all!  I've
> not looked at the patch yet.
>
>> Thanks Rafael. I think we still need Mark's Ack for the ASoC codec changes
>> though before we can proceed.
>
> Probably the easiest thing would be a tag for the core change that I can
> pull.

Or you can apply them both if that helps (please consider the first
one as ACKed in that case).