From: Edward Cree <ecree@solarflare.com>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: linux-pci <linux-pci@vger.kernel.org>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Don Dutile <ddutile@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Vasundhara Volam <vasundhara.volam@emulex.com>
Subject: Re: [PATCH] PCI: handle pci_sriov_set_totalvfs(dev, 0)
Date: Mon, 4 Aug 2014 16:45:16 +0100 [thread overview]
Message-ID: <53DFAA8C.2010602@solarflare.com> (raw)
In-Reply-To: <107835EF-8941-4621-952F-E1583F7E3636@gmail.com>
On 02/08/14 01:25, Ethan Zhao wrote:
> 在 2014年8月1日，下午8:15，Edward Cree <ecree@solarflare.com> 写道：
>> On 01/08/14 04:51, Ethan Zhao wrote:
>>> So far seems no driver call pci_sriov_set_totalvfs() with numvfs = 0
>>> and the patch will change the behavior of the drivers, but it will
>>> definitely change the test cases and documents related to IOV.
>> As for test cases and documents, I can't find any in the kernel tree
> I mean some test cases or doc that are out of kernel tree ... such as some Distro,
> not only Hardware vendors.
I was under the impression that we don't care about breaking out-of-tree
code. Distros should be (and it looks like most are) using the
kernel-doc to generate their documentation, and the kernel-doc doesn't
say anything about what happens when passing 0.
-Edward
next prev parent reply other threads:[~2014-08-04 15:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53D9288B.5030302@solarflare.com>
2014-07-30 18:05 ` pci_sriov_set_totalvfs again Don Dutile
2014-07-30 18:24 ` Edward Cree
2014-07-30 21:14 ` Alexander Duyck
2014-07-31 12:07 ` Edward Cree
2014-07-31 14:24 ` [PATCH] PCI: handle pci_sriov_set_totalvfs(dev, 0) Edward Cree
2014-07-31 15:21 ` Alexander Duyck
2014-07-31 15:56 ` Edward Cree
2014-07-31 16:40 ` Alexander Duyck
2014-07-31 16:57 ` Edward Cree
2014-07-31 17:53 ` Don Dutile
2014-07-31 18:13 ` Edward Cree
2014-08-04 14:03 ` Edward Cree
2014-08-04 14:37 ` Alexander Duyck
2014-08-04 15:22 ` Edward Cree
2014-08-06 9:38 ` Don Dutile
2014-07-31 17:55 ` Alexander Duyck
2014-07-31 18:24 ` Edward Cree
2014-08-01 3:18 ` Ethan Zhao
2014-08-01 11:51 ` Edward Cree
2014-08-02 0:34 ` Ethan Zhao
2014-08-01 3:51 ` Ethan Zhao
2014-08-01 12:15 ` Edward Cree
2014-08-02 0:25 ` Ethan Zhao
2014-08-04 15:45 ` Edward Cree [this message]
2014-08-04 16:40 ` Alexander Duyck
2014-08-04 17:08 ` Edward Cree
2014-08-04 6:53 ` Sathya Perla
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=53DFAA8C.2010602@solarflare.com \
--to=ecree@solarflare.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=ethan.kernel@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=vasundhara.volam@emulex.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.