| 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
| ||
|
Date: Fri, 26 Jun 2015 09:23:27 -0700 From: "Luis R. Rodriguez" <mcgrof@...e.com> To: "Marciniszyn, Mike" <mike.marciniszyn@...el.com>, Borislav Petkov <bp@...e.de>, Ingo Molnar <mingo@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk> Cc: Doug Ledford <dledford@...hat.com>, "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Deprecating ipath On Fri, Jun 26, 2015 at 9:17 AM, Marciniszyn, Mike <mike.marciniszyn@...el.com> wrote: > Doug, > > We have been given the go ahead to start the deprecation process for thie ipath driver. That's great! Do you mean removal from Linux? > What do I need to do to get that done? Feature removal txt file was removed from the kernel so there is no "schedule" per se, not sure what the process these days is for driver removal. How about punting it to staging for a release or two and then remove it? Not sure if that would be frowned upon or welcomed. That would have the cost of moving history through directories but git --follow helps with that these days. The gain of moving it to staging IMHO would be that if anyone who might care would need to complain may do so for a directory change for 1-2 release may spot this easily and the issues would be much less than an immediate removal. Luis -- 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