-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stephen Hemminger wrote:
On a related topic. Why not figure out a way to embed the tapsets
into the kernel source (a.l.a Docbook)?
Sure, why not. The only problem is to come up with a notation which
isn't too invasive. Frank's example showed one problem tapsets are
supposed to solve: make parameters available under a name which doesn't
change. Another goal for them is to make commonly used expressions
derived from the state when entering the function available (e.g., inode
belonging to a file descriptor).
This kind of information might need a single line for each convenience
variable defined in the tapset. So, it should be manageable.