On Sun, Apr 22, 2001 at 02:42:29PM +0100, Matthew Kirkwood wrote:
> On Sun, 22 Apr 2001, Russell King wrote:
> > And what would:
> >
> > C: CONFIG_ARM
> >
> > tell you? Nothing that is not described in the rest of the "ARM PORT"
> > entry.
>
> True, but it would tell it to a script without intervention.
I'll grant you that it does solve the "who owns a CONFIG_ symbol", but
that is only one small problem - there's the bigger problem as to who
owns each line of code. Are we going to start labelling each source
code line as well?
I just don't see what this gets us - its safe to assume that any symbol
in arch/*/config.in which isn't a driver is looked after by the
architecture maintainer. If not, the architecture maintainer probably
knows who does.
If the purpose of this "documentation" exercise for CONFIG_* symbols
is just that, then shouldn't we be adding it to the Config.in files,
rather than creating yet more files which will become out of sync
with the configuration system? (maybe we are, but the suggestions
I've seen appear to the contary).
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
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 : Mon Apr 23 2001 - 21:00:42 EST