From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Rick Boone <rick@buzz-media.com>,
xen-devel@lists.xensource.com, konrad.wilk@oracle.com
Subject: Re: TMEM + pv_ops kernel?
Date: Sat, 15 May 2010 16:07:38 -0700 [thread overview]
Message-ID: <4BEF293A.3070805@goop.org> (raw)
In-Reply-To: <b7fac401-162b-428a-9db5-05a08f5a0c49@default>
On 05/15/2010 03:36 PM, Dan Magenheimer wrote:
>> Since the tmem patches seem to be settling down, I was waiting a bit to
>> see if they get into an upstreamable state for this next merge window
>> (though that's getting pretty tight at this point). But if we can set
>> up
>> a git branch based on 2.6.32 we should be able to easily merge it into
>> all the various pvops branches. Are there any tmem changes needed
>> between .32 and later kernels?
>>
> Sometimes the patches don't apply perfectly cleanly to later kernels,
> but maybe git automatically handles merges better than "patch"?
>
Yeah, that shouldn't be a problem.
J
next prev parent reply other threads:[~2010-05-15 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 22:16 TMEM + pv_ops kernel? Rick Boone
[not found] ` <614bc626-d7e1-449a-bcbe-3f783f52dcd6@default 4BEDD0E0.8070502@buzz-media.com>
2010-05-14 15:26 ` Dan Magenheimer
2010-05-14 22:38 ` Rick Boone
2010-05-14 22:59 ` Dan Magenheimer
2010-05-15 1:13 ` Rick Boone
2010-05-15 20:03 ` Jeremy Fitzhardinge
2010-05-15 22:36 ` Dan Magenheimer
2010-05-15 23:07 ` Jeremy Fitzhardinge [this message]
2010-05-15 10:22 ` Pasi Kärkkäinen
2010-05-15 18:44 ` Rick Boone
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=4BEF293A.3070805@goop.org \
--to=jeremy@goop.org \
--cc=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=rick@buzz-media.com \
--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.