> I'd be happy to take another swing at this problem once the kbuild-2.5/CML2
> transition is done. But I don't think we should let it block us from
> having the good results we can get from that change.
It would certainly fit nicely with the existing metadata. We already rip out
code comments via kernel-doc, and extending it to rip out
- Help text
- Web site
- Version information
- Man page for the driver
- Module options
etc, shouldn't be too challenging. Ok so kernel-doc is in perl and ugly perl
but if someone hates it enough to rewrite it in python thats a win too 8)
Alan
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
