On Wed, 12 Sep 2007, David Newall wrote: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) | \ $ 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 ======================================================================== -
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Eric W. Biederman | [PATCH 0/10] sysfs network namespace support |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
