[lkml]   [2007]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/7] lguest: documentation pt I: Preparation
> Items for consideration would be:
> - if this stuff is good, shouldn't other code be using it? If so, is
> this new infrastructure in the correct place?
> - if, otoh, this infrastructure is _not_ suitable for other code, well,
> what was wrong with it?
> - if the requirement is good, perhaps alternative implementations should
> be explored (dunno what).

Well, we could just rewrite the whole kernel in Web and judge all future
patches on how literate they are...

Seriously, though, even if the (small) infrastructure is not going to
take over the driver tree anytime soon, it's hard to imagine why we
would not want to incorporate this sort of documentation. It's good
stuff, something which can really help people get a sense for how this
whole virtualization thing works. And it makes the code fun to read.


P.S. I am currently considering a no-limericks policy for the LWN quote
of the week.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-07-24 17:15    [W:0.135 / U:7.404 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site