All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 1/7] lguest documentation: infrastructure and Chapter I
Date: Thu, 7 Jun 2007 23:23:49 -0700	[thread overview]
Message-ID: <20070607232349.b4673058.akpm@linux-foundation.org> (raw)
In-Reply-To: <1181272257.24958.12.camel@localhost.localdomain>

On Fri, 08 Jun 2007 13:10:57 +1000 Rusty Russell <rusty@rustcorp.com.au> wrote:

> The netfilter code had very good documentation: the Netfilter Hacking
> HOWTO.  Noone ever read it.
> 
> So this time I'm trying something different, using a bit of
> Knuthiness.
> 
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> ---
>  Documentation/lguest/extract          |   58 +++++++++++++++++++++++++++++++++
>  Documentation/lguest/lguest.c         |    9 +++--
>  drivers/lguest/Makefile               |   12 ++++++
>  drivers/lguest/README                 |   47 ++++++++++++++++++++++++++
>  drivers/lguest/core.c                 |    7 ++-
>  drivers/lguest/hypercalls.c           |    9 +++--
>  drivers/lguest/interrupts_and_traps.c |   13 +++++++
>  drivers/lguest/io.c                   |    8 +++-
>  drivers/lguest/lguest.c               |   31 ++++++++++++++++-
>  drivers/lguest/lguest_bus.c           |    3 +
>  drivers/lguest/lguest_user.c          |    7 +++
>  drivers/lguest/page_tables.c          |   10 ++++-
>  drivers/lguest/segments.c             |   11 ++++++
>  drivers/lguest/switcher.S             |   13 +++----
>  14 files changed, 219 insertions(+), 19 deletions(-)

This patch series craps all over the existing one:

lguest-export-symbols-for-lguest-as-a-module.patch
lguest-the-guest-code.patch
lguest-the-host-code.patch
lguest-the-asm-offsets.patch
lguest-the-makefile-and-kconfig.patch
lguest-the-console-driver.patch
lguest-the-net-driver.patch
lguest-the-block-driver.patch
lguest-the-documentation-example-launcher.patch

obviously we could append this new series to the existing one, but that
limits our ability to make further changes over the next few weeks.  Or we
just give up trying to present the series nicely and it hits mainline with
a random stream of uninteresting and irrelevant afterthoughts at the end,
like we're some lameo git users or something.

(I could split all this up, but I'm getting kinda bored of preventing you
from mucking up your own patch series)

So... what course dost thou wish to take?

  parent reply	other threads:[~2007-06-08  6:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08  3:10 [PATCH 1/7] lguest documentation: infrastructure and Chapter I Rusty Russell
2007-06-08  3:11 ` [PATCH 2/7] lguest documentation:Chapter II Rusty Russell
2007-06-08  3:11 ` Rusty Russell
2007-06-08  3:12   ` [PATCH 3/7] lguest documentation:Chapter III Rusty Russell
2007-06-08  3:12   ` Rusty Russell
2007-06-08  3:13     ` [PATCH 4/7] lguest documentation:Chapter IV Rusty Russell
2007-06-08  3:13       ` [PATCH 5/7] lguest documentation:Chapter V Rusty Russell
2007-06-08  3:14         ` [PATCH 6/7] lguest documentation:Chapter VI Rusty Russell
2007-06-08  3:14         ` Rusty Russell
2007-06-08  3:15           ` [PATCH 7/7] lguest documentation:Chapter VII Rusty Russell
2007-06-08  3:15           ` Rusty Russell
2007-06-08  3:13       ` [PATCH 5/7] lguest documentation:Chapter V Rusty Russell
2007-06-08  6:23 ` [PATCH 1/7] lguest documentation: infrastructure and Chapter I Andrew Morton
2007-06-08  6:23 ` Andrew Morton [this message]
2007-06-08  7:05   ` Rusty Russell
2007-06-08  7:05   ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2007-06-08  3:10 Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070607232349.b4673058.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.