public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Paolo 'Blaisorblade' Giarrusso" <blaisorblade@yahoo.it>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH 00/14] UML: simple changes for 2.6.19
Date: Mon, 9 Oct 2006 14:11:01 -0400	[thread overview]
Message-ID: <20061009181101.GD4931@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20061005213212.17268.7409.stgit@memento.home.lan>

On Thu, Oct 05, 2006 at 11:32:12PM +0200, Paolo 'Blaisorblade' Giarrusso wrote:
> This is the first set of patches for UML for 2.6.19 I send - I have various
> other patches to merge but I'm sending them in separate batches to avoid
> flooding.

ACK to all of these, except for the first one (moving the inclusion of
the arch Makefile), which seems wrong to me.

				Jeff

      parent reply	other threads:[~2006-10-10  2:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 21:32 [PATCH 00/14] UML: simple changes for 2.6.19 Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:38 ` [PATCH 01/14] uml: fix compilation options for USER_OBJS Paolo 'Blaisorblade' Giarrusso
2006-10-09 16:32   ` [uml-devel] " Jeff Dike
2006-10-11 11:08     ` Paolo Giarrusso
2006-10-13 20:10       ` Jeff Dike
2006-10-26  6:08         ` Blaisorblade
2006-10-05 21:38 ` [PATCH 02/14] uml: revert wrong patch Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:45   ` Andi Kleen
2006-10-05 21:45     ` [uml-devel] " Blaisorblade
2006-10-05 21:38 ` [PATCH 03/14] uml: correct removal of pte_mkexec Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:38 ` [PATCH 04/14] uml: readd forgot prototype Paolo 'Blaisorblade' Giarrusso
2006-10-06  1:00   ` Andrew Morton
2006-10-09 18:12     ` [uml-devel] " Jeff Dike
2006-10-05 21:38 ` [PATCH 05/14] uml: make TT mode compile after setjmp-related changes Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:38 ` [PATCH 06/14] uml: make UML_SETJMP always safe Paolo 'Blaisorblade' Giarrusso
2006-10-09 18:00   ` [uml-devel] " Jeff Dike
2006-10-14  0:13     ` Blaisorblade
2006-10-05 21:38 ` [PATCH 07/14] uml: fix processor selection to exclude unsupported processors and features Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:38 ` [PATCH 08/14] uml: fix uname under setarch i386 Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:39 ` [PATCH 09/14] uml: declare in Kconfig our partial LOCKDEP support Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:39 ` [PATCH 10/14] uml: allow using again x86/x86_64 crypto code Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:39 ` [PATCH 11/14] uml: asm offsets duplication removal Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:39 ` [PATCH 12/14] uml: remove duplicate export Paolo 'Blaisorblade' Giarrusso
2006-10-05 21:39 ` [PATCH 13/14] uml: deprecate CONFIG_MODE_TT Paolo 'Blaisorblade' Giarrusso
2006-10-09 18:05   ` [uml-devel] " Jeff Dike
2006-10-05 21:39 ` [PATCH 14/14] uml: allow finer tuning for host VMSPLIT setting Paolo 'Blaisorblade' Giarrusso
2006-10-09 18:11 ` Jeff Dike [this message]

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=20061009181101.GD4931@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox