lkml.org 
[lkml]   [2001]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
>>>>> "Eric" == Eric S Raymond <esr@thyrsus.com> writes:

Eric> Alan Cox <alan@lxorguk.ukuu.org.uk>:
>> Many of your 'broken' symbols arent. We have no idea what the real
>> amount is

Eric> If it can't be mechanically verified that the symbol has a
Eric> correct reference pattern within the tree, then it's broken.
Eric> That's a definition.

It's a definition but not necessarily the best one to follow.

Eric> The fact that it might become un-broken someday, by somebody's
Eric> intention to merge in future code, is interesting but irrelevant
Eric> to the fact that symbols broken in present time *mask bugs* in
Eric> present time.

Symbols that are not referenced at all by the code does not hide any
bugs. They might make it take longer time for people to configure
their kernel but thats about it.

This does not mean that obsolete symbols should not be removed,
however running around telling people to remove symbols that they
might be using in their tree does cause unnecessary work for the
people who are writing the code.

Jes
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:27    [W:0.158 / U:0.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site