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]

Message-ID: <20110503220233.GB14080@kroah.com>
Date:	Tue, 3 May 2011 15:02:33 -0700
From:	Greg KH <greg@...ah.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/23] intel_sst: Save audio state across D3 on Medfield

On Tue, May 03, 2011 at 10:53:16PM +0100, Alan Cox wrote:
> > 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.

That sounds like a good idea.

Mark, can you try to let me know if you are patching staging code?  If
you want to "own" a driver in the staging tree, that's fine, just let me
konw and I'll funnel patches to you for it (we do that for other staging
drivers).

It's just that for times like this, when I have no idea that someone
else modified it in linux-next, and then patches fail to apply, that it
gets messy.

thanks,

greg k-h
--
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/