From: john slee <indigoid@higherplane.net>
To: Harald Welte <laforge@gnumonks.org>
Cc: Jonathan Lundell <jlundell@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Documentation of module parameters.
Date: Sat, 21 Apr 2001 03:30:19 +1000 [thread overview]
Message-ID: <20010421033019.N10345@higherplane.net> (raw)
In-Reply-To: <3ADBB8C9.CC7FD941@nc.rr.com> <p05100b07b7017fc83c2e@[207.213.214.34]> <20010420133722.D2461@tatooine.laforge.distro.conectiva> <20010421031920.M10345@higherplane.net>
In-Reply-To: <20010421031920.M10345@higherplane.net>; from indigoid@higherplane.net on Sat, Apr 21, 2001 at 03:19:20AM +1000
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
On Sat, Apr 21, 2001 at 03:19:20AM +1000, john slee wrote:
> it sounded like a challenge. this might help someone who can't be
and it might be even more helpful if it didnt appear with a stupid
mimetype.
attempt #2
--
"Bobby, jiggle Grandpa's rat so it looks alive, please" -- gary larson
[-- Attachment #2: kernel-module-info.sh --]
[-- Type: text/plain, Size: 311 bytes --]
#!/bin/sh
# john slee <indigoid@higherplane.net>
# Sat Apr 21 03:17:55 EST 2001
# quick and dirty. run from a kernel source dir somewhere.
find . -name "*.c" | xargs egrep 'MODULE_DESCRIPTION|MODULE_PARM_DESC' \
| sed '/#undef/d; s/^\.\///; s/[:()]/ /g; s/[";]//g; /MODULE_PARM_DESC/s/,[ ]*/ /; /^[ ]*$/d'
next prev parent reply other threads:[~2001-04-20 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 3:30 Documentation of module parameters Chris Kloiber
2001-04-17 5:07 ` Jonathan Lundell
2001-04-20 16:37 ` Harald Welte
2001-04-20 17:19 ` john slee
2001-04-20 17:30 ` john slee [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20010421033019.N10345@higherplane.net \
--to=indigoid@higherplane.net \
--cc=jlundell@pobox.com \
--cc=laforge@gnumonks.org \
--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