All of lore.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk, sam@ravnborg.org
Subject: Should MODULE_DESCRIPTION be mandatory ?
Date: Wed, 15 Apr 2009 13:11:46 +0200	[thread overview]
Message-ID: <671646821@web.de> (raw)

Hi, 

some time ago i spotted that around 20% of the Linux modules lacking a MODULE_DESCRIPTION field.  ( http://bugzilla.kernel.org/show_bug.cgi?id=10770 )

I think it`s not a practicable approach to get this fixed by some single person digging trough all the modules. 
If itŽs fixed for a kernel release, one year later there would be another bunch of new modules lacking the description field again.

What about a build-time or run-time warning for missing MODULE_DESCRIPTION ? (as it exists for MODULE_LICENSE in modpost.c) 

Wouldn`t that solve the "problem" automatically as time goes by ?

regards
Roland








____________________________________________________________________
Psssst! Schon vom neuen WEB.DE MultiMessenger gehört? 
Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123


             reply	other threads:[~2009-04-15 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 11:11 devzero [this message]
2009-04-15 19:42 ` Should MODULE_DESCRIPTION be mandatory ? Sam Ravnborg
2009-04-15 21:15   ` Randy Dunlap
2009-04-15 21:21     ` Sam Ravnborg
2009-04-15 21:26       ` Randy Dunlap
2009-04-16 12:27         ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2009-04-15 21:59 devzero
2009-04-16 11:25 ` Sam Ravnborg

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=671646821@web.de \
    --to=devzero@web.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.