| 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: <20080120192356.GI8669@does.not.exist> Date: Sun, 20 Jan 2008 21:23:57 +0200 From: Adrian Bunk <bunk@...nel.org> To: gerg@...inux.org, Miles Bader <miles@....org> Cc: linux-kernel@...r.kernel.org Subject: RFC: Removal of the v850 port? Is anyone maintaining the v850 port in the Linux kernel or will work on getting it back into a usable state in the foreseeable future? Otherwise I'll send a patch to remove it. That's not meant personally against anyone, and it would not prevent the port from getting back into the kernel in the future if someone will start getting it back into a usable state, but in it's current state it is simply useless. cu Adrian ----- Forwarded message from Adrian Bunk <bunk@...nel.org> ----- Date: Tue, 1 Jan 2008 15:50:21 +0200 From: Adrian Bunk <bunk@...nel.org> To: Miles Bader <miles@....org> Cc: linux-kernel@...r.kernel.org Subject: Status of the v850 port? Trying to compile the v850 port brings you many compile errors, one of them exists since at least kernel 2.6.19. Are there any patches in some external tree that should be merged? Or will anyone work on getting this port back into a usable state in the forseeable future? Otherwise the only reasonable option would be to remove this port from the kernel sources since it is dead code. cu Adrian ----- End forwarded message ----- -- 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