All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 3/3] xen: use direct ops on 64-bit
Date: Fri, 30 Jan 2009 23:22:17 -0800	[thread overview]
Message-ID: <4983FC29.9040907@goop.org> (raw)
In-Reply-To: <4983E313.4070902@gmail.com>

Tejun Heo wrote:
> Jeremy Fitzhardinge wrote:
>   
>> Enable the use of the direct vcpu-access operations on 64-bit.
>>
>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>>     
>
> Hmmm... these three patches conflict with the previous two patches.
> I'll soon send out a new tree.  Can you please wait a bit and refresh
> the patches?

Sorry about that; I had to do a fair amount of hacking to get things 
going in the end.  I mailed out those other patches prematurely after 
"testing" them with the wrong kernel.

I'll send updated fixes when I see your changes appear in tip.git.

    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Brian Gerst <brgerst@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] xen: use direct ops on 64-bit
Date: Fri, 30 Jan 2009 23:22:17 -0800	[thread overview]
Message-ID: <4983FC29.9040907@goop.org> (raw)
In-Reply-To: <4983E313.4070902@gmail.com>

Tejun Heo wrote:
> Jeremy Fitzhardinge wrote:
>   
>> Enable the use of the direct vcpu-access operations on 64-bit.
>>
>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>>     
>
> Hmmm... these three patches conflict with the previous two patches.
> I'll soon send out a new tree.  Can you please wait a bit and refresh
> the patches?

Sorry about that; I had to do a fair amount of hacking to get things 
going in the end.  I mailed out those other patches prematurely after 
"testing" them with the wrong kernel.

I'll send updated fixes when I see your changes appear in tip.git.

    J

  reply	other threads:[~2009-01-31  7:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31  1:42 [PATCH 3/3] xen: use direct ops on 64-bit Jeremy Fitzhardinge
2009-01-31  5:35 ` Tejun Heo
2009-01-31  7:22   ` Jeremy Fitzhardinge [this message]
2009-01-31  7:22     ` Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2009-02-02 21:55 Jeremy Fitzhardinge

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=4983FC29.9040907@goop.org \
    --to=jeremy@goop.org \
    --cc=brgerst@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=xen-devel@lists.xensource.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.