From: Harald Welte <laforge@gnumonks.org>
To: Jonathan Lundell <jlundell@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Documentation of module parameters.
Date: Fri, 20 Apr 2001 13:37:22 -0300 [thread overview]
Message-ID: <20010420133722.D2461@tatooine.laforge.distro.conectiva> (raw)
In-Reply-To: <3ADBB8C9.CC7FD941@nc.rr.com> <p05100b07b7017fc83c2e@[207.213.214.34]>
In-Reply-To: <p05100b07b7017fc83c2e@[207.213.214.34]>; from jlundell@pobox.com on Mon, Apr 16, 2001 at 10:07:56PM -0700
On Mon, Apr 16, 2001 at 10:07:56PM -0700, Jonathan Lundell wrote:
> At 11:30 PM -0400 2001-04-16, Chris Kloiber wrote:
> >I was recently looking for a single location where all the possible
> >module parameters for the linux kernel was located.
>
> Hear him. A DocBook document would be a dandy place for this to get pulled
> together, too.
good idea. One could just grab all the MODULE_PARM_DESC out of all sourcefiles,
look to which module the particular sourcefile belongs (looking into
Makefile?), and create a Documentation/DocBook/... document out of it.
Sounds like something doable, only somebody needs to get around doing
it. Any volunteers?
> --
> /Jonathan Lundell.
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
next prev parent reply other threads:[~2001-04-20 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 3:30 Chris Kloiber
2001-04-17 5:07 ` Jonathan Lundell
2001-04-20 16:37 ` Harald Welte [this message]
2001-04-20 17:19 ` john slee
2001-04-20 17:30 ` john slee
2001-04-17 16:24 coop
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=20010420133722.D2461@tatooine.laforge.distro.conectiva \
--to=laforge@gnumonks.org \
--cc=jlundell@pobox.com \
--cc=linux-kernel@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 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®