mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cantab.net>
To: Alexander Viro <viro@math.psu.edu>
Cc: Christian Kurz <shorty@getuid.de>, linux-kernel@vger.kernel.org
Subject: Re: modules missing author name and/or description
Date: Sat, 10 Aug 2002 13:20:01 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20020810131745.00b2e320@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0208100758290.9847-100000@weyl.math.psu.edu>

At 13:04 10/08/02, Alexander Viro wrote:
>On Sat, 10 Aug 2002, Christian Kurz wrote:
> > I just played with lsmod and modinfo and noticed that the following
> > modules which I use either lack one or both of the information I
> > mentioned in the description. The following modules lack the name of the
> > author:
>
>[snip the list]
>
>Quite a few modules don't _have_ a single author.  MODULE_AUTHOR is
>optional and very dubious at that - especially since we already have
>a common way to put attributions in there; just look at the comments
>in the beginning of almost any file in the tree.

Yes, MODULE_MAINTAINER would be way more useful than MODULE_AUTHOR anyway, 
so you know whom to contact about bugs, even when you don't have source 
code at hand to lookup MAINTAINERS file... The original author can be long 
gone and moved onto other things...

Best regards,

         Anton


-- 
   "I've not lost my mind. It's backed up on tape somewhere." - Unknown
-- 
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/


  reply	other threads:[~2002-08-10 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-10  9:14 Christian Kurz
2002-08-10 12:04 ` Alexander Viro
2002-08-10 12:20   ` Anton Altaparmakov [this message]
2002-08-10 12:21   ` Roman Zippel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.2.20020810131745.00b2e320@pop.cus.cam.ac.uk \
    --to=aia21@cantab.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shorty@getuid.de \
    --cc=viro@math.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®