From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Smith Subject: Re: [PATCH 00/17] Netchannel2 for a modern git kernel Date: Wed, 7 Oct 2009 20:17:09 +0100 Message-ID: <20091007191709.GA10568@weybridge.uk.xensource.com> References: <4AC92B44.5020208@goop.org> <20091005092937.GA1036@weybridge.uk.xensource.com> <4ACA638A.5060209@goop.org> <20091006090616.GA21511@weybridge.uk.xensource.com> <20091006163543.GA12403@weybridge.uk.xensource.com> <4ACB7A68.9030306@goop.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1506961099==" Return-path: In-Reply-To: <4ACB7A68.9030306@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Steven Smith , "xen-devel@lists.xensource.com" , Keir Fraser , "joserenato.santos@hp.com" List-Id: xen-devel@lists.xenproject.org --===============1506961099== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > >>> 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 mak= es > >>> 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 m= ost > >>> specific one that covers the dependencies (xen/core, xen/dom0/core, f= or > >>> example). > >>> =20 > >> 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? > >> =20 > > 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. --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKzOk1vAgSWYI3DVMRAryuAKCeCmaPbqFt+7QQcTjimtPizfHfZwCfWlDu YAbF9FYiLwN+yk46heeT41Y= =Zxjb -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- --===============1506961099== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1506961099==--