All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Smith <steven.smith@citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Steven Smith <Steven.Smith@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	"joserenato.santos@hp.com" <joserenato.santos@hp.com>
Subject: Re: [PATCH 00/17] Netchannel2 for a modern git kernel
Date: Wed, 7 Oct 2009 20:17:09 +0100	[thread overview]
Message-ID: <20091007191709.GA10568@weybridge.uk.xensource.com> (raw)
In-Reply-To: <4ACB7A68.9030306@goop.org>


[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]

> >>> 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).
> >>>       
> >> I needed to make some changes to netback to make forwarding packets
> >> between NC1 and NC2 interfaces work, but apart from that it's fairly
> >> self-contained.  Would you like me to rebase to
> >> xen/dom0/backend/netback?
> >>     
> > Hmm... xen/dom0/backend/netback doesn't actually boot on my test box,
> > so that could be a little tricky:
> Yeah, I wouldn't expect the netback to boot on its own.  It is
> functionally self-contained, but it doesn't have the other functionality
> of the other branches.
Okay.  It took me a little while to figure out how to make git do the
desired thing, but the nc2/rebased-pq branch should now contain the
patch series, including the last set of interface changes, rebased
against xen/dom0/backend/netback.

Thank you for the hints.

Steven.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2009-10-07 19:17 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
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 [this message]
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=20091007191709.GA10568@weybridge.uk.xensource.com \
    --to=steven.smith@citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Steven.Smith@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=joserenato.santos@hp.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.