From: Zachary Amsden <zach@vmware.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21
Date: Mon, 05 Feb 2007 20:54:17 -0800 [thread overview]
Message-ID: <45C809F9.2090905@vmware.com> (raw)
In-Reply-To: <1170736029.29293.31.camel@localhost.localdomain>
Rusty Russell wrote:
> On Mon, 2007-02-05 at 19:52 -0800, Zachary Amsden wrote:
>
>> A bunch of VMI and paravirt-ops bugfixes for upstream. Also, fix the
>> timer code to work for 2.6.21, which had a number of changes.
>>
>> These should mostly be non-controversial and beneficial to all the
>> paravirt-ops work.
>>
>
> Indeed, I'm expecting to push lguest this week, and this code will
> effect me, so I'd like to see this in a -mm soon...
>
> Thanks!
> Rusty.
>
Yes, I took a look at the lguest changes today and I think these won't
generate conflicts, just make stuff easier for you ;) Course you've now
got a couple new paravirt-ops to support, but the native ones are fine
for temporary use.
Cheers,
Zach
next prev parent reply other threads:[~2007-02-06 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:52 [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21 Zachary Amsden
2007-02-06 4:27 ` Rusty Russell
2007-02-06 4:54 ` Zachary Amsden [this message]
2007-02-06 5:11 ` Rusty Russell
2007-02-06 5:24 ` Stephen Rothwell
2007-02-06 9:07 ` Arjan van de Ven
2007-02-06 9:25 ` Zachary Amsden
2007-02-06 12:25 ` Andi Kleen
2007-02-06 12:45 ` Arjan van de Ven
2007-02-06 18:16 ` Andi Kleen
2007-02-13 22:39 ` Rik van Riel
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=45C809F9.2090905@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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