mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: David Newall <david@davidnewall.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stripping down the kernel-parameters.txt file
Date: Wed, 12 Sep 2007 10:06:35 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709120951280.22891@localhost.localdomain> (raw)
In-Reply-To: <46E7EA62.5020604@davidnewall.com>

On Wed, 12 Sep 2007, David Newall wrote:

> Robert P. J. Day wrote:
> > if the goal is to simply put all of the basic boot-time kernel parms
> > along with the module-specific ones into a single file, sorted in
> > alphabetical order, then i contend that this is, in fact, "silly".
>
> Or even, "messy".  There's no doubt that it should be maintained
> with care; perhaps it would if the people who write the code for
> each parameter also update the documentation.

  or (and here's a wild and crazy idea) what about writing a utility
that auto-generates all that information?

  the biggest hassle in keeping all the documentation up to date is
that much of it is being stored in a manually-updated text file
(MAINTAINERS leaps to mind), so *of course* it's always going to be
out of date.  so why not just fix it so it's auto-generated, the same
way the in-kernel nano-doc stuff is?

  surely, it wouldn't be that hard, at least for the basic parms.  a
combination of egrep, sed and sort would certainly give you the basic
parms.  off the top of my head:

$ egrep '(__setup|early_param)' $(find . -name *.c) | \
> sed -e 's/.*"\(.*\)".*/\1/' | \
> sort -u
$

  of course that's not sufficient, but it took me all of two minutes.
would it be that much work to extend it and deal with once and for
all?

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

  reply	other threads:[~2007-09-12 14:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12  7:50 Robert P. J. Day
2007-09-12 12:43 ` David Newall
2007-09-12 13:11   ` Robert P. J. Day
2007-09-12 13:32     ` David Newall
2007-09-12 14:06       ` Robert P. J. Day [this message]
2007-09-12 14:30     ` Rogan Dawes
2007-09-12 14:44       ` Robert P. J. Day
2007-09-12 17:47         ` Kyle Moffett
2007-09-12 17:56           ` Randy Dunlap

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=Pine.LNX.4.64.0709120951280.22891@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=david@davidnewall.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®