From: domen@coderock.org
To: linux-kernel@vger.kernel.org
Cc: damm@opensource.se
Subject: [patch 0/5] autoparam v0.2: generating parameter descriptions on compile
Date: Thu, 07 Jul 2005 13:25:51 +0200 [thread overview]
Message-ID: <20050707112551.331553000@homer> (raw)
Hi!
The purpose of autoparam is to generate boot parameter descriptions
from sources. It does that by creating a new section called
__param_strings. (The interesting bits here are from Magnus Damm.)
It fills a gap about undocumented boot options from modules.
It consists of 5 patches:
autoparam_1-includes
Descriptions get saved in __param_strings. Also added a new
__setup_desc().
autoparam_2-makefile
On every vmlinux change .kernel-parameters.o gets regenerated, and
__param_strings removed from vmlinux. (It's still bigger than
non-patched vmlinux, but all sections are of same length, alignment
issues?)
Also, a new target "make kernelparams" which generates
Documentation/kernel-parameters-gen.txt. It should probably not be
in $(srctree) though.
There should be some more work done here, but I'm out of ideas ATM.
autoparam_3-extract_script
Simple perl script to extract descriptions.
autoparam_4-af_unix_workaround
autoparam_5-ide_workaround
Workarounds needed.
Comments, improvements?
Domen
next reply other threads:[~2005-07-07 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 11:25 domen [this message]
2005-07-07 11:25 ` [patch 1/5] autoparam: includes domen
2005-07-07 11:25 ` [patch 2/5] autoparam: makefile domen
2005-07-07 11:25 ` [patch 3/5] autoparam: extract script domen
2005-07-07 11:25 ` [patch 4/5] autoparam: af_unix workaround domen
2005-07-07 17:13 ` Alexey Dobriyan
2005-07-07 11:25 ` [patch 5/5] autoparam: ide workarounds domen
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=20050707112551.331553000@homer \
--to=domen@coderock.org \
--cc=damm@opensource.se \
--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®