On Thu, 24 Jul 2003, John Bradford wrote:
> i wrote:
> > and in the end, while i know some folks don't think it's a big
> > deal, i think doing a "make allyesconfig" really should work.
>
> It's _counter productive_ just to bodge it so that make allyesconfig
> works. I _want_ it to _fail_ if the drivers are _broken_.
>
> A CONFIG_KNOWN_BROKEN option is a good thing, in the case where,
> E.G. a SCSI driver is broken, and will randomly corrupt data, but
> otherwise compiles and appears to work. Apart from that, it's a
> complete waste of time to fiddle around with silly options that do
> nothing but bloat the codebase and waste developers' time.
whoa, calm down. i didn't mean to start that kind of flame war. for the
record, i feel that, if something is *known* to be broken, it should not
be in the source tree. naturally, in the testing process, there will
be stuff that has bugs, which is why we test. but i'm just not buying
the argument of leaving modules like riscom8 in the tree for release
after release when it hasn't compiled properly for as long as i can
remember.
but the impression i've gotten so far is that some folks are adamant that
some broken/non-updated/legacy/obsolete/whatever code will remain in the
source tree because it might be fixed *some day*. if that's the case,
then i think such code should be marked or tagged *somehow* as being
broken.
it's a matter of public perception -- it looks bad to ship code that
is *known* not to compile.
and on that note, i'll let this one go. my $0.02. $0.03 canadian.
rday
p.s. and, yes, i think "make allyesconfig" should just plain work
for official release kernels. so there. :-P
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:23 EST