From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Rose, Gregory V" <gregory.v.rose@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.0.1-rc4 and stable 2.6.32.x pvops won't start xend
Date: Tue, 20 Jul 2010 11:05:22 -0700 [thread overview]
Message-ID: <4C45E562.9070203@goop.org> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755F15103AF@orsmsx508.amr.corp.intel.com>
On 07/20/2010 09:10 AM, Rose, Gregory V wrote:
> OK, I was working off of a special branch created by Jeremy to test the SR-IOV patches that allow for setting the VF MAC and VLAN from the host VMM using RTNETLINK messages and netdev ops. That branch doesn't include the gntdev.c device. When I switched back to the xen/stable-2.6.32.x branch it was back again. My confusion I guess, I was under the impression Jeremy's sr-iov branch was based on the stable-2.6.32.x branch that I had originally posted my patches against. Evidently they're not.
>
No, I rebased it to plain kernel.org v2.6.32, since there were no other
Xen dependencies in your changes.
J
prev parent reply other threads:[~2010-07-20 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 21:48 Xen 4.0.1-rc4 and stable 2.6.32.x pvops won't start xend Rose, Gregory V
2010-07-20 9:05 ` Pasi Kärkkäinen
2010-07-20 15:52 ` Rose, Gregory V
2010-07-20 16:10 ` Rose, Gregory V
2010-07-20 17:20 ` Pasi Kärkkäinen
2010-07-20 18:05 ` Jeremy Fitzhardinge [this message]
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=4C45E562.9070203@goop.org \
--to=jeremy@goop.org \
--cc=gregory.v.rose@intel.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.