Richard Knutsson wrote:Oh no, did'n mean like that. All entries in the Kconfig has a "config CONFIG_FLAG" (of course ;) ) and so *config "knows" which flag to search for (if added to MAINTAINERS, that is).
Stefan Richter wrote:
On 15 Jan, Matthias Schniedermeyer wrote:I think it could be practical to have an easy access to whom is
Stefan Richter wrote:Or, "click here to say 'it does not work'"?
On 14 Jan, Richard Knutsson wrote:Having "all(tm)" information of something in one place?
(Really liked the idea to have a "Maintainer"-button next to "Help"Rhetorical question: What will this button be used for?
in *config)
My rhetorical question wasn't about what it is intended for, but what
people would think it was intended for if it was there.
responsible for a driver and which mailinglist its development is
addressed to, both for people interested in helping develop the driver
and those who got an error (or fan-mail :).
Yes, this is a bit out of scope, but just realized a simple way toI think adding the Maintainers-data is more or less a logical next step.Seems more like what you actually want to have there is links to users'
It's not always clear from the MAINTAINERS-file who is the right person
for what. Especially as it is a rather large text-file with only
mediocre search-friendlieness. It's a 3.5 K-lines file!
So when you know that you have a problem with drivers X, wouldn't it be
great if you could just "go to" the driver in *config and see not only
the Help-Text but the Maintainers-Data also.
mailinglists or forums.
When this thread started, it was about assisting authors in submitting
patches.
implement it if using the CONFIG_FLAG-approach, just "grep" after the
flag, under which the user hit the "Maintainer"-button, in the
MAINTAINER-file. Also, I think this solves the handler-problem since an
entry can have multiple CONFIG_FLAG's stated.
I don't think we should add the maintainer-entries directly in Kconfig,
as you Stefan stated, because it is for configure the kernel. With the
above approach, it will just require minor fixes in the "make *config"
to handle it.
But how do you suppose the user gets the CONFIG_-String, which the user
then could for searching?
I'd say only a small percentage of hardcore-users would use the
.config-file directly, the others would deviate over *config, so i'd say
if the MAINTAINERS-data is integrated into Kconfig it's the perfect(tm)
90% solution.
OTOH you could just teach the *config to lookup a MAINTAINERS-entry when
all they are properly flagged.