| 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
| ||
|
Message-ID: <20110503184032.GK1762@opensource.wolfsonmicro.com> Date: Tue, 3 May 2011 19:40:32 +0100 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: greg@...ah.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/23] Intel SST driver update On Tue, May 03, 2011 at 07:36:12PM +0100, Alan Cox wrote: > Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote: > > What's the plan for moving these out of staging? Quite a few of these > > patches feel like moves in the wrong direction, adding more code that's > > going to have problems with mainline rather than addressing the issues > > that prevent merges. > There is a separate driver being written. In the meantime this driver is > getting updated and maintained because in the real world people have > customers and products to deliver. Sure, I was just asking if there was a plan to work on this properly - the normal expectation in staging is that we'll see in place refactoring and this series clearly isn't that. You seem a little defensive here... > It might as well therefore be maintained in tree as out. That seems to > serve Linux users rather better. Of course, as do most of us, I was mostly making sure that there was a plan here. -- 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/
Powered by blists - more mailing lists