All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Zachary Amsden <zach@vmware.com>,
	hch@infradead.org, ak@suse.de, linux-kernel@vger.kernel.org,
	riel@redhat.com, chrisw@osdl.org, pratap@vmware.com
Subject: Re: [PATCH] 8/8 Create MMU 2/3 level accessors in the sub-arch layer (i386)
Date: Sat, 6 Aug 2005 16:02:27 -0700	[thread overview]
Message-ID: <20050806230227.GC7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050806155832.28f77c37.akpm@osdl.org>

* Andrew Morton (akpm@osdl.org) wrote:
> Yup, with one or two semi-exceptions, all the patches up to this series
> seem to be good general cleanups - certainly it's good to move all those
> open-coded asm statements into single-site inlines and macros: people keep
> on screwing them up.

I agree.

> We do need to wake the Xen poeple up, make sure that these changes suit
> them as well, or at least don't screw them over (hard to see how it could
> though).

I have a series of similar patches that I've done for Xen that I'll
post shortly.

thanks,
-chris

  reply	other threads:[~2005-08-06 23:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42F46558.9010202@vmware.com.suse.lists.linux.kernel>
2005-08-06 11:37 ` [PATCH] 8/8 Create MMU 2/3 level accessors in the sub-arch layer (i386) Andi Kleen
2005-08-06 11:56   ` Christoph Hellwig
2005-08-06 11:58     ` Andi Kleen
2005-08-06 12:01       ` Christoph Hellwig
2005-08-06 18:28         ` Zachary Amsden
2005-08-06 22:58           ` Andrew Morton
2005-08-06 23:02             ` Chris Wright [this message]
2005-08-07 10:39             ` Zachary Amsden
2005-08-06  7:23 Zachary Amsden
2005-08-07  1:16 ` Chris Wright

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=20050806230227.GC7762@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratap@vmware.com \
    --cc=riel@redhat.com \
    --cc=zach@vmware.com \
    /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.