> >>> 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.
signature.asc
Description: Digital signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home