Re: [PATCH 1/7] lguest: documentation pt I: Preparation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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.

jon

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux