From: Yijing Wang <wangyijing@huawei.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
Rafael <rjw@sisk.pl>, Hanjun Guo <guohanjun@huawei.com>,
<jiang.liu@huawei.com>
Subject: Re: [PATCH -v2 0/3] Use PCIe DSN to improve pciehp_resume
Date: Mon, 15 Jul 2013 08:51:17 +0800 [thread overview]
Message-ID: <51E34785.20703@huawei.com> (raw)
In-Reply-To: <1373710849.1352.29.camel@x61.thuisdomein>
On 2013/7/13 18:20, Paul Bolle wrote:
> Yijing,
>
> On Fri, 2013-07-12 at 09:52 +0800, Yijing Wang wrote:
>> Do you wireless card support Device Serial Number ?
>> You can confirm it by lspci -vvv.
>
> Yes, it does:
> lspci -vvv -s 03:00 | grep Serial
> Capabilities: [140 v1] Device Serial Number [...]
>
OK, I got it, thanks!
>
> Paul Bolle
>
>
>
--
Thanks!
Yijing
prev parent reply other threads:[~2013-07-15 0:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:43 [PATCH -v2 0/3] Use PCIe DSN to improve pciehp_resume Yijing Wang
2013-07-11 9:43 ` [PATCH -v2 1/3] PCI: introduce PCIe Device Serial Number Capability support Yijing Wang
2013-07-11 9:51 ` Don Dutile
2013-07-11 20:09 ` Bjorn Helgaas
2013-07-11 18:18 ` Don Dutile
2013-07-12 2:39 ` Yijing Wang
2013-07-12 3:37 ` Bjorn Helgaas
2013-07-12 2:30 ` Yijing Wang
2013-07-12 1:38 ` Yijing Wang
2013-07-12 2:43 ` Don Dutile
2013-07-11 14:22 ` Paul Bolle
2013-07-12 1:55 ` Yijing Wang
2013-07-11 9:43 ` [PATCH -v2 2/3] PCI,pciehp: avoid add a device already exist before suspend during resume Yijing Wang
2013-07-11 14:27 ` Paul Bolle
2013-07-12 2:19 ` Yijing Wang
2013-07-11 9:43 ` [PATCH -v2 3/3] PCI,pciehp: use PCIe DSN to identify device change during suspend Yijing Wang
2013-07-11 10:04 ` Don Dutile
2013-07-11 14:33 ` Paul Bolle
2013-07-12 2:19 ` Yijing Wang
2013-07-11 14:19 ` [PATCH -v2 0/3] Use PCIe DSN to improve pciehp_resume Paul Bolle
2013-07-12 1:52 ` Yijing Wang
2013-07-13 10:20 ` Paul Bolle
2013-07-15 0:51 ` Yijing Wang [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=51E34785.20703@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rjw@sisk.pl \
/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.