From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/5] IB/hfi1: use pci_reset_bus() for initiating pci secondary bus reset
Date: Wed, 20 Jun 2018 00:12:55 -0400 [thread overview]
Message-ID: <1529467995-28780-2-git-send-email-okaya@codeaurora.org> (raw)
In-Reply-To: <1529467995-28780-1-git-send-email-okaya@codeaurora.org>
Getting ready to hide pci_reset_bridge_secondary_bus() from the drivers.
pci_reset_bridge_secondary_bus() should only be used internally by the
PCI code itself.
Other drivers should rely on higher level pci_reset_xxx() API.
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
---
drivers/infiniband/hw/hfi1/pcie.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/infiniband/hw/hfi1/pcie.c b/drivers/infiniband/hw/hfi1/pcie.c
index 4d4371b..a6d695a 100644
--- a/drivers/infiniband/hw/hfi1/pcie.c
+++ b/drivers/infiniband/hw/hfi1/pcie.c
@@ -905,9 +905,7 @@ static int trigger_sbr(struct hfi1_devdata *dd)
* delay after a reset is required. Per spec requirements,
* the link is either working or not after that point.
*/
- pci_reset_bridge_secondary_bus(dev->bus->self);
-
- return 0;
+ return pci_reset_bus(dev->bus);
}
/*
--
2.7.4
next prev parent reply other threads:[~2018-06-20 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 4:12 [PATCH V2 1/5] PCI: handle error return from pci_reset_bridge_secondary_bus() Sinan Kaya
2018-06-20 4:12 ` Sinan Kaya [this message]
2018-06-20 4:12 ` [PATCH V2 3/5] PCI: Hide pci_reset_bridge_secondary_bus() from drivers Sinan Kaya
2018-06-20 4:12 ` [PATCH V2 4/5] PCI: Unify try slot and bus reset API Sinan Kaya
2018-06-20 4:12 ` [PATCH V2 5/5] PCI: Unify " Sinan Kaya
2018-06-20 5:17 ` kbuild test robot
2018-06-21 4:58 ` kbuild test robot
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=1529467995-28780-2-git-send-email-okaya@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).