From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jiang Liu <liuj97@gmail.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Xudong Hao <xudong.hao@intel.com>,
Yijing Wang <wangyijing@huawei.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Jiang Liu <jiang.liu@huawei.com>
Subject: Re: [PATCH 2/3] PCI, ACPI: Don't glue ACPI dev with pci VFs
Date: Tue, 4 Jun 2013 15:08:09 -0700 [thread overview]
Message-ID: <CAE9FiQWBxm1bz2=gR_rho642qJVoWrxCSkc1YW-banwPBWXirg@mail.gmail.com> (raw)
In-Reply-To: <CAErSpo6GBw4C3mXRrd_f=6GFnEwhH7tHcAkp+ib=HMwVPpc0=w@mail.gmail.com>
On Tue, Jun 4, 2013 at 3:00 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> On Tue, Jun 4, 2013 at 3:57 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> Well, I read that in the changelog, but that doesn't tell me what bad
> things happen as a result. Can you elaborate a little bit? Does it
> mean PM doesn't work, hotplug doesn't work, drivers can't bind to the
> VFs correctly, the magic smoke comes out of the PF, or what?
no, I did not notice anything unusual except the binding message.
as my platform have those PM disabled.
next prev parent reply other threads:[~2013-06-04 22:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 4:21 [PATCH 1/3] PCI: set correct value for iov device before device Jiang Liu
2013-05-31 4:21 ` [PATCH 2/3] PCI, ACPI: Don't glue ACPI dev with pci VFs Jiang Liu
2013-05-31 21:40 ` Bjorn Helgaas
2013-06-04 21:48 ` Bjorn Helgaas
2013-06-04 21:57 ` Yinghai Lu
2013-06-04 22:00 ` Bjorn Helgaas
2013-06-04 22:08 ` Yinghai Lu [this message]
2013-06-04 22:44 ` Rafael J. Wysocki
2013-06-04 22:49 ` Rafael J. Wysocki
2013-06-04 22:57 ` Yinghai Lu
2013-06-04 23:51 ` Rafael J. Wysocki
2013-06-05 15:55 ` Yinghai Lu
2013-06-05 16:21 ` Bjorn Helgaas
2013-05-31 4:21 ` [PATCH 3/3] PCI: Hide remove and rescan sysfs interfaces for SR-IOV virtual functions Jiang Liu
2013-06-05 18:32 ` Bjorn Helgaas
2013-06-05 18:31 ` [PATCH 1/3] PCI: set correct value for iov device before device Bjorn Helgaas
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='CAE9FiQWBxm1bz2=gR_rho642qJVoWrxCSkc1YW-banwPBWXirg@mail.gmail.com' \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=jiang.liu@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=rjw@sisk.pl \
--cc=wangyijing@huawei.com \
--cc=xudong.hao@intel.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).