linux-kernel - Re: [PATCH 01/23] intel_sst: Save audio state across D3 on Medfield

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:	Tue, 3 May 2011 22:53:16 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/23] intel_sst: Save audio state across D3 on Medfield

> To recap the previous discussion: staging is just not in the slightest
> bit viable for ASoC stuff, code that does anything non-trivial is going

Yes I know that - and its active development of a nice clean driver going
on upstream so doesn't belong there anyway. The ASoC driver should
probably have its own copy of the bits of the staging driver that it
needs however.

I can fix this collision up easily enough and if doing it not via the
rules is best fine by me. I think it might be wiser however if the ASoC
driver took its own copy of the bits it actually needed.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/