From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Andi Kleen <ak@suse.de>
Subject: Re: Paravirt-ops next steps
Date: Thu, 09 Nov 2006 19:48:06 -0800 [thread overview]
Message-ID: <4553F676.4030303@vmware.com> (raw)
In-Reply-To: <20061109193744.94d7afa2.akpm@osdl.org>
Andrew Morton wrote:
> It'd be better to develop and test this work on top of Thomas's stuff, as
> that's what 2.6.20 will doubtless look like. That means working against
> -mm. Once Thomas's patches are in mainline then the patches will apply to
> Andi's tree too and I can send them over to him.
>
> That way, the patch-applying-order equals mainstream-merging-order equals
> chronological-writing-order, which is generally a good thing.
>
Sounds sane. Are Thomas's patches in -rc5-mm1? If so, we should rebase
paravirt-ops, although I don't want to lose any paravirt patches that
you've dropped because they were merged to Andi. Don't know if that is
the case, but I did see a bunch of "merged into a subsystem tree" drops
from -mm related to paravirt.
Thanks,
Zach
next prev parent reply other threads:[~2006-11-10 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 3:27 Paravirt-ops next steps Zachary Amsden
2006-11-10 3:37 ` Andrew Morton
2006-11-10 3:48 ` Zachary Amsden [this message]
2006-11-10 3:58 ` Andrew Morton
2006-11-10 4:16 ` Zachary Amsden
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=4553F676.4030303@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=virtualization@lists.osdl.org \
/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).