linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	glommer@gmail.com, tglx@linutronix.de, ehabkost@redhat.com,
	jeremy@goop.org, avi@qumranet.com, anthony@codemonkey.ws,
	virtualization@lists.linux-foundation.org, rusty@rustcorp.com.au,
	ak@suse.de, chrisw@sous-sol.org, rostedt@goodmis.org,
	hpa@zytor.com, zach@vmware.com
Subject: Re: [PATCH 0/3] Unify segment headers
Date: Fri, 7 Dec 2007 21:41:02 +0100	[thread overview]
Message-ID: <20071207204102.GA25424@elte.hu> (raw)
In-Reply-To: <119704456265-git-send-email-gcosta@redhat.com>


* Glauber de Oliveira Costa <gcosta@redhat.com> wrote:

> Hi,
> 
> In this patch, I unify segment_32.h and segment_64.h into segment.h 
> They have some common parts, but a considerable ammount of code still 
> has to be around ifdefs.
> 
> The only patch that is really important to paravirt is the first one, 
> that moves a paravirt definition into the common header. The other two 
> are just normal integration, and pretty much independent

thanks, i've picked them up for x86.git.

	Ingo

      parent reply	other threads:[~2007-12-07 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 16:22 [PATCH 0/3] Unify segment headers Glauber de Oliveira Costa
2007-12-07 16:22 ` [PATCH 1/3] [PATCH] put get_kernel_rpl in a common location Glauber de Oliveira Costa
2007-12-07 16:22   ` [PATCH 2/3] [PATCH] unify common parts of segment.h Glauber de Oliveira Costa
2007-12-07 16:22     ` [PATCH 3/3] [PATCH] remove arch specific segment headers Glauber de Oliveira Costa
2007-12-07 20:41 ` Ingo Molnar [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=20071207204102.GA25424@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=chrisw@sous-sol.org \
    --cc=ehabkost@redhat.com \
    --cc=gcosta@redhat.com \
    --cc=glommer@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).