From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Steven Smith <steven.smith@citrix.com>
Cc: Steven Smith <Steven.Smith@eu.citrix.com>,
"keir.fraser@citrix.com" <keir.fraser@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"joserenato.santos@hp.com" <joserenato.santos@hp.com>
Subject: Re: [PATCH 00/17] Netchannel2 for a modern git kernel
Date: Mon, 05 Oct 2009 14:22:18 -0700 [thread overview]
Message-ID: <4ACA638A.5060209@goop.org> (raw)
In-Reply-To: <20091005092937.GA1036@weybridge.uk.xensource.com>
On 10/05/09 02:29, Steven Smith wrote:
>>> This is a forward port of the NC2 patches I posted against so that
>>> they apply to Jeremy's git tree, rather than the XCI patchqueue. It's
>>> identical in most important respects, except that I've not included
>>> any of the VMQ patches.
>>>
>> Do you have a git tree I can pull these from? I have
>> git://xenbits.xensource.com/people/ssmith/netchannel2-pvops.git in my
>> list of repos, but you don't seem to have updated it.
>>
> Oops, sorry about that. It should all be in now, in the nc2/master
> branch.
>
> (Although you may want to wait until the discussion about the new
> grant table interface is sorted out before pulling.)
>
Thanks. I've pulled it anyway, but not yet merged it into anything yet.
What dependencies does it have on the rest of the xen changes? In
general I like to avoid basing branches on xen/master, because it makes
them fairly brittle to rebase or otherwise rearrange. Ideally I like to
base each topic branch on a mainline kernel version (like v2.6.31), or
if there are too many dependencies on other Xen topic branches, the most
specific one that covers the dependencies (xen/core, xen/dom0/core, for
example).
Also, does this include both front and backend parts together? I think
it would be easier to deal with if you could split it into separate
common, frontend and backend branches. Or maybe that would be too fiddly...
J
next prev parent reply other threads:[~2009-10-05 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1254667618.git.ssmith@weybridge.uk.xensource.com>
2009-10-04 15:04 ` [PATCH 10/17] Transmit and receive checksum offload support steven.smith
2009-10-04 23:09 ` [PATCH 00/17] Netchannel2 for a modern git kernel Jeremy Fitzhardinge
2009-10-05 9:29 ` Steven Smith
2009-10-05 21:22 ` Jeremy Fitzhardinge [this message]
2009-10-06 9:06 ` Steven Smith
2009-10-06 16:35 ` Steven Smith
2009-10-06 17:12 ` Jeremy Fitzhardinge
2009-10-07 19:17 ` Steven Smith
2009-10-06 17:06 ` Jeremy Fitzhardinge
2009-10-07 8:15 ` Steven Smith
2009-10-20 6:00 ` Jeremy Fitzhardinge
2009-10-20 9:40 ` Steven Smith
2009-10-23 22:06 ` 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=4ACA638A.5060209@goop.org \
--to=jeremy@goop.org \
--cc=Steven.Smith@eu.citrix.com \
--cc=joserenato.santos@hp.com \
--cc=keir.fraser@citrix.com \
--cc=steven.smith@citrix.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.