Re: MODULE_MAINTAINER

Adrian Bunk
2007-04-04T16:38:09Z

On Wed, Apr 04, 2007 at 06:33:06PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Wed, Apr 04, 2007 at 03:02:41PM +0200, Rene Herman wrote:
> >> Given modules with multiple authors, current and non-current, I believe
> >> having "modinfo -m" tell the user whom to contact is an avantage.
> >
> > Much bigger problems are:
> > - Who will maintain this information properly?
> > - What about modules that are maintained implicitely by the subsystem
> > maintainer?
> >
> > And often a user can't be expected to locate the source of a problem, or
> > it might not be in a driver but in a subsystem.
> >
> > For vendor kernels, the user should contact the vendor.
> > For ftp.kernel.org kernels, I don't see any better solution than telling
> > people to report problems to linux-kernel or the kernel Bugzilla and
> > routing them further from here.
>
> Generelly it has to be kept in mind that there are different contacts
> for different purposes:
> - usage problems --> get in touch with the _support_
> - bug reports --> get in touch with _maintainers_

- bug reports against vendor kernels -> get in touch with the _vendor_
(the vendor might ship a heavily patched driver in an ancient kernel)

> - development --> get in touch with maintainers/ kernel hackers/
> copyright holders...
>
> The Amiga keyboard had a [Help] key, but this is not how it works.

> Stefan Richter

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed