All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] adding missing MODULE_* stuffs
Date: Wed, 04 Jan 2006 05:43:26 +0000	[thread overview]
Message-ID: <20060104054325.GB898@kroah.com> (raw)
In-Reply-To: <20051230000400.GS18040@outflux.net>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Tue, Jan 03, 2006 at 09:18:16PM -0800, Kees Cook wrote:
> On Tue, Jan 03, 2006 at 08:27:09PM -0800, Greg KH wrote:
> > I said that?  Hm, looks like Jean did, not I :)
> 
> Oh, whoops.  I scrolled up just enough to find your name.  ;)
> 
> > > Notably, AUTHOR, DESCRIPTION, and VERSION seem to be missing from the 
> > > various examples in Documention/
> > 
> > What examples?
> 
> i2c/porting-clients (instructions, rather than code)
> i2c/writing-clients (same)
> sound/alsa/DocBook/writing-an-alsa-driver.tmpl
> firmware_class/firmware_sample_driver.c
> firmware_class/firmware_sample_firmware_class.c
> connector/cn_test.c
> DocBook/kernel-hacking.tmpl (not really an example, more a description)
> DocBook/videobook.tmpl
> DocBook/procfs_example.c
> kprobes.txt
> 
> What I was really in the mood for was adding those things to the rest of 
> the code tree too.  There are plenty of modules that have authors, 
> versions, and descriptions listed in comments and #define's, but not 
> marked up in MODULE_*() syntax.

Sure, start in a directory and work through them all :)

Good luck,

greg k-h

[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-01-04  5:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30  0:04 [KJ] adding missing MODULE_* stuffs Kees Cook
2006-01-04  1:13 ` Greg KH
2006-01-04  5:18 ` Kees Cook
2006-01-04  5:43 ` Greg KH [this message]
2006-01-08 20:45 ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Alexey Dobriyan
2006-01-08 20:45   ` Alexey Dobriyan
2006-01-08 21:55   ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* Carlos Manuel Duclos Vergara
2006-01-08 21:55     ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Carlos Manuel Duclos Vergara
2006-01-08 21:58     ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* Greg KH
2006-01-08 21:58       ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Greg KH
2006-01-08 22:32       ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* Matt Domsch
2006-01-08 22:32         ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Matt Domsch
2006-01-08 22:33         ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* Matt Domsch
2006-01-08 22:33           ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Matt Domsch
2006-01-08 22:03     ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* Matthew Wilcox
2006-01-08 22:03       ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Matthew Wilcox
2006-01-08 23:41     ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* Håkon Løvdal
2006-01-08 23:41       ` MODULE_VERSION useless? (was Re: [KJ] adding missing MODULE_* stuffs) Håkon Løvdal

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=20060104054325.GB898@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@vger.kernel.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.