summaryrefslogtreecommitdiffstats
path: root/fs/ext4/extents.c
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2009-02-22 23:19:12 +0100
committerIngo Molnar <mingo@elte.hu>2009-02-23 00:54:01 +0100
commit965c7ecaf2e2b083d711a01ab33735a4bdeee1a4 (patch)
treeb83609b1b39195df4711114b520c3dde5c37ea2e /fs/ext4/extents.c
parent8425091ff8af2addae118fc510a523b84ce51115 (diff)
downloadlinux-965c7ecaf2e2b083d711a01ab33735a4bdeee1a4.tar.gz
linux-965c7ecaf2e2b083d711a01ab33735a4bdeee1a4.tar.bz2
linux-965c7ecaf2e2b083d711a01ab33735a4bdeee1a4.zip
x86: remove the Voyager 32-bit subarch
Impact: remove unused/broken code The Voyager subarch last built successfully on the v2.6.26 kernel and has been stale since then and does not build on the v2.6.27, v2.6.28 and v2.6.29-rc5 kernels. No actual users beyond the maintainer reported this breakage. Patches were sent and most of the fixes were accepted but the discussion around how to do a few remaining issues cleanly fizzled out with no resolution and the code remained broken. In the v2.6.30 x86 tree development cycle 32-bit subarch support has been reworked and removed - and the Voyager code, beyond the build problems already known, needs serious and significant changes and probably a rewrite to support it. CONFIG_X86_VOYAGER has been marked BROKEN then. The maintainer has been notified but no patches have been sent so far to fix it. While all other subarchs have been converted to the new scheme, voyager is still broken. We'd prefer to receive patches which clean up the current situation in a constructive way, but even in case of removal there is no obstacle to add that support back after the issues have been sorted out in a mutually acceptable fashion. So remove this inactive code for now. Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'fs/ext4/extents.c')
0 files changed, 0 insertions, 0 deletions