From: Don Dutile <ddutile@redhat.com>
To: Yuval Mintz <yuvalmin@broadcom.com>
Cc: "Rose, Gregory V" <gregory.v.rose@intel.com>,
Alexander Duyck <alexander.duyck@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"bhutchings@solarflare.com" <bhutchings@solarflare.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [RFC v2] PCI: sysfs per device SRIOV control and status
Date: Thu, 25 Oct 2012 09:19:27 -0400 [thread overview]
Message-ID: <50893C5F.7000308@redhat.com> (raw)
In-Reply-To: <50878105.8000503@broadcom.com>
On 10/24/2012 01:47 AM, Yuval Mintz wrote:
>>> I've finished some patches for the ixgbe driver and they are under internal review. Testing turned out pretty well. Hopefully they'll be ready for posting tomorrow afternoon since I'm gone Thursday and Friday. They'll be based on your RFC v2 patch. I don't expect many changes will be required for the next version of your patch.
>>>
>>> - Greg
>>>
>> Great!
>> I'll work on re-doing the patch set to have just the two sysfs files
>> as discussed above.
>> We can make an incremental change to move the sriov_enable/disable since
>> your patch has it ready to do just that.
>
> Hi,
>
> I've failed to find [RFC v3]; Will such a series be sent in the imminent future?
>
> Thanks,
> Yuval
>
>
Sorry for delay... (many) customers getting in the way again! ;-)
I'll be posting a V3 set shortly.
Testing w/patches Greg Rose gave me for ixgbe to fully exercise the
good & failure paths, so the V3 set should be in good functional
shape; just finished the testing late last night.
next prev parent reply other threads:[~2012-10-25 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 22:14 [RFC v2] PCI: sysfs per device SRIOV control and status Donald Dutile
2012-10-04 22:30 ` Yinghai Lu
2012-10-04 22:50 ` Don Dutile
2012-10-04 23:05 ` Yinghai Lu
2012-10-05 15:10 ` Don Dutile
2012-10-06 18:21 ` Alexander Duyck
2012-10-08 15:44 ` Greg Rose
2012-10-09 18:39 ` Don Dutile
2012-10-09 20:31 ` Rose, Gregory V
2012-10-09 22:49 ` Don Dutile
2012-10-24 5:47 ` Yuval Mintz
2012-10-25 13:19 ` Don Dutile [this message]
2012-10-09 16:12 ` Don Dutile
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=50893C5F.7000308@redhat.com \
--to=ddutile@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=bhelgaas@google.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=yuvalmin@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).