| 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: <20110503212749.1d72f9b9@lxorguk.ukuu.org.uk> Date: Tue, 3 May 2011 21:27:49 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> Cc: greg@...ah.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/23] Intel SST driver update > 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... There I disagree (on both points). We have a collection of drivers in staging some of which are in the 'refactor and move' category (eg SEP) others of which are in the 'until the nice one is done' category - eg much of the wireless stuff, rim4 and a few other drivers. > > 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. Yes there is a plan. SST essentially gets updated to fix stuff that needs to work (eg runtime PM for Moorestown) but isn't the future. My favourite sst patch is going to be the one which reads 'added 0 lines, removed bazillions' because at that point it ceases to be my problem ;) 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/
Powered by blists - more mailing lists