what about adding a "[BROKEN]" tag to the short line descriptions of
config options, like "(NEW)" and "[EXEPERIMENTAL]" or "[DANGEROUS]"?
It should be used for config options that are known to currently not
compile at all.
That way, you could play with development kernels without the need to
recompile it three or four times, just because you realize: "Oh, yes, I
forgot, matrox_fb currently doesn't compile..."
(matrox_fb is actually a quite good example presently)
Don't misunderstand, the option should not be mandatory for everything
that doesn't compile (or just compiles under certain circumstances),
just for things that are really known to not compile at all, i.e. we
know that matrox_fb simply isn't ready yet in the current development
kernels and this even has been discussed in this mailing list.
Of course, this only makes really sense for development kernels, on
stable kernels everything should compile or else it's a bug (and nobody
knows that it won't compile)
To distinguish things better, this tag should only be for things that
don't COMPILE, wether they actually work or not. One might think about
introducing another tag for things that do compile but actually don't
work properly - meaning everything from "simply does nothing" to
"completely burn out your workstation case and shoot it into space" -
but I don't know if that really makes sense since in that situation it's
hard to say wether something will provide the desired functionality. (If
it always did, we wouldn't need development kernels :) )
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/