All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Don Dutile <ddutile@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Rafael <rjw@sisk.pl>, Hanjun Guo <guohanjun@huawei.com>,
	Jiang Liu <jiang.liu@huawei.com>
Subject: Re: [PATCH -v2 1/3] PCI: introduce PCIe Device Serial Number Capability support
Date: Fri, 12 Jul 2013 10:30:32 +0800	[thread overview]
Message-ID: <51DF6A48.4070506@huawei.com> (raw)
In-Reply-To: <CAErSpo50ni41TiscZDVpg8wMFK2wgWmS1sySfNTs8X9JA7Mmkw@mail.gmail.com>

>> }
>>>
>>> +       pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_DSN);
>>> +       if (!pos)
>>> +               return 0;
>>> +
>>> +       pci_read_config_dword(dev, pos + 4,&lo);
>>> +       pci_read_config_dword(dev, pos + 8,&hi);
>>> +       sn = ((u64)hi<<  32) | lo;
>>
>> See comment below:
>>         dev->sn = ((u64)hi<<  32) | lo;
>>         return;
>>
>>> +       return sn;
>>> +}
>>> +EXPORT_SYMBOL(pci_device_serial_number);
>>> +
>>> +/**
>>>    * pci_configure_ari - enable or disable ARI forwarding
>>>    * @dev: the PCI device
>>>    *
>>> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>>> index 46ada5c..c4c1a2b 100644
>>> --- a/drivers/pci/probe.c
>>> +++ b/drivers/pci/probe.c
>>> @@ -1322,6 +1322,8 @@ static void pci_init_capabilities(struct pci_dev
>>> *dev)
>>>         /* Power Management */
>>>         pci_pm_init(dev);
>>>
>>> +       dev->sn = pci_device_serial_number(dev);
>>> +
>>
>> Finally, 'the comment below':
>> I know you were following Bjorn's suggestion, which I thought
>> was an improvement, but why not do above assignment in
>> pci_device_serial_number() ?
>> See above....
> 
> pci_device_serial_number() would then have the side-effect of saving
> the result somewhere, and callers would have to know where to look.
> Personally, I think it's simpler to return the serial number directly
> and avoid the side-effect, but maybe this is just bike-shedding.
> 
> As long as we are bike-shedding, I'd just drop "sn" and do:
> 
>     return ((u64)hi << 32) | lo;
> 
> And of course, you need spaces before "&hi" and "&lo" in the
> pci_read_config_dword() calls.

OK, will drop "sn", strangely my original patch has spaces before "&hi" and "&lo",
but in reply the spaces disappeared.

Thanks!
Yijing.


> 



> .
> 


-- 
Thanks!
Yijing


  parent reply	other threads:[~2013-07-12  2:31 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 [this message]
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

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=51DF6A48.4070506@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=ddutile@redhat.com \
    --cc=guohanjun@huawei.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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.