From: "lindar_liu" <lindar_liu@usish.com>
To: 'Yijing Wang' <wangyijing@huawei.com>,
"'James E.J. Bottomley'" <JBottomley@parallels.com>
Cc: 'Hanjun Guo' <guohanjun@huawei.com>,
jiang.liu@huawei.com, xjtuwjp@gmail.com,
linux-scsi@vger.kernel.org
Subject: RE: [PATCH 11/16] pm8001: clean up unnecessary MSI/MSI-X capability find
Date: Fri, 9 Aug 2013 10:57:58 +0800 [thread overview]
Message-ID: <00aa01ce94ac$412320b0$c3696210$@com> (raw)
In-Reply-To: <1375967421-26540-1-git-send-email-wangyijing@huawei.com>
On 08/08/2013 9:10 PM, Yijing Wang wrote:
> PCI core will initialize device MSI/MSI-X capability in
> pci_msi_init_pci_dev(). So device driver should use pci_dev-
> >msi_cap/msix_cap to determine whether the device support MSI/MSI-X
> instead of using pci_find_capability(pci_dev, PCI_CAP_ID_MSI/MSIX).
> Access to PCIe device config space again will consume more time.
>
It's fine.
You can add my Acked-by.
Thanks,
Lindar
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> Cc: xjtuwjp@gmail.com
> Cc: lindar_liu@usish.com
> Cc: "James E.J. Bottomley" <JBottomley@parallels.com>
> Cc: linux-scsi@vger.kernel.org
> ---
> drivers/scsi/pm8001/pm8001_init.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/pm8001/pm8001_init.c
> b/drivers/scsi/pm8001/pm8001_init.c
> index 3861aa1..1ee61e8 100644
> --- a/drivers/scsi/pm8001/pm8001_init.c
> +++ b/drivers/scsi/pm8001/pm8001_init.c
> @@ -734,7 +734,7 @@ static u32 pm8001_request_irq(struct
> pm8001_hba_info *pm8001_ha)
> pdev = pm8001_ha->pdev;
>
> #ifdef PM8001_USE_MSIX
> - if (pci_find_capability(pdev, PCI_CAP_ID_MSIX))
> + if (pdev->msix_cap)
> return pm8001_setup_msix(pm8001_ha);
> else {
> PM8001_INIT_DBG(pm8001_ha,
> --
> 1.7.1
next prev parent reply other threads:[~2013-08-09 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:10 [PATCH 11/16] pm8001: clean up unnecessary MSI/MSI-X capability find Yijing Wang
2013-08-09 2:57 ` lindar_liu [this message]
2013-08-09 7:30 ` 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='00aa01ce94ac$412320b0$c3696210$@com' \
--to=lindar_liu@usish.com \
--cc=JBottomley@parallels.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=wangyijing@huawei.com \
--cc=xjtuwjp@gmail.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.