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/stable-2.6.32.x PATCH 0/5] SR-IOV: Backport VF MAC and VLAN configuration to 2.6.32.x
Date: Thu, 15 Jul 2010 14:12:04 -0700 [thread overview]
Message-ID: <4C3F79A4.20905@goop.org> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755EA961372@orsmsx508.amr.corp.intel.com>
On 07/15/2010 10:34 AM, Rose, Gregory V wrote:
>> -----Original Message-----
>> From: Jeremy Fitzhardinge [mailto:jeremy@goop.org]
>> Sent: Thursday, July 15, 2010 10:31 AM
>> To: Rose, Gregory V
>> Cc: 'xen-devel@lists.xensource.com'
>> Subject: Re: [Xen-devel] [xen/stable-2.6.32.x PATCH 0/5] SR-IOV:
>> Backport VF MAC and VLAN configuration to 2.6.32.x
>>
>> On 07/15/2010 10:13 AM, Rose, Gregory V wrote:
>>
>>>> -----Original Message-----
>>>> From: Jeremy Fitzhardinge [mailto:jeremy@goop.org]
>>>> Sent: Thursday, July 15, 2010 10:05 AM
>>>> To: Rose, Gregory V
>>>> Cc: 'xen-devel@lists.xensource.com'
>>>> Subject: Re: [Xen-devel] [xen/stable-2.6.32.x PATCH 0/5] SR-IOV:
>>>> Backport VF MAC and VLAN configuration to 2.6.32.x
>>>>
>>>> On 07/14/2010 01:59 PM, Rose, Gregory V wrote:
>>>>
>>>>
>>>>> This series of patches is a back port of patches originally inluded
>>>>> in the Linux 2.6.34 kernel to the xen/2.6.32.x branch. Authors of
>>>>> the original patches are CC'd.
>>>>>
>>>>> The purpose of the patches is to allow configuration of SR-IOV
>>>>>
>> virtual
>>
>>>>> function MAC address and VLAN ID via the physical function driver in
>>>>> those drivers that support SR-IOV and export the required netdev ops
>>>>> functions.
>>>>>
>>>>> The commits from the original patches in the Linux 2.6.34 kernel git
>>>>> logs are:
>>>>>
>>>>> commit fb8a0d9d1bfd1e4355f307e86a6da7209eefd5f3
>>>>> commit b280da8d54b8d82b52f368a8703b7ada6c1744d5
>>>>> commit 95c26df829ba4a25f40595cadb4c9433883cbe28
>>>>> commit ebc08a6f47ee76ecad8e9f26c26e6ec9b46ca659
>>>>> commit c02db8c6290bb992442fec1407643c94cc414375
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>> Do you have a git tree I can pull these from?
>>>>
>>>>
>>>>
>>> They're in Linus' git tree at kernel.org.
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
>>>
>>>
>> I meant the backported versions. Or do they just rebase with no effort?
>>
> Oh, excuse me, I misunderstood.
>
> The patches I posted should apply cleanly to your tree on the xen/stable-2.6.32.x branch as of yesterday. If they don't I can rebase them and re-send.
>
I just cherry-picked the original patches onto v2.6.32 and pushed the
results as the "sr-iov" branch. Please check it and I'll merge it in
when you give the all-clear.
Thanks,
J
next prev parent reply other threads:[~2010-07-15 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 20:59 [xen/stable-2.6.32.x PATCH 0/5] SR-IOV: Backport VF MAC and VLAN configuration to 2.6.32.x Rose, Gregory V
2010-07-14 21:47 ` Rose, Gregory V
2010-07-15 17:04 ` Jeremy Fitzhardinge
2010-07-15 17:13 ` Rose, Gregory V
2010-07-15 17:31 ` Jeremy Fitzhardinge
2010-07-15 17:34 ` Rose, Gregory V
2010-07-15 21:12 ` Jeremy Fitzhardinge [this message]
2010-07-15 21:32 ` Rose, Gregory V
2010-07-16 19:19 ` Rose, Gregory V
2010-07-16 20:07 ` Rose, Gregory V
2010-07-16 20:57 ` Rose, Gregory V
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=4C3F79A4.20905@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.