From: Kelsey Skunberg <skunberg.kelsey@gmail.com>
To: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
skunberg.kelsey@gmail.com
Cc: skhan@linuxfoundation.org, rafael.j.wysocki@intel.com,
keith.busch@intel.com
Subject: [PATCH 0/2] PCI: Change to using pci_dev_is_inaccessible()
Date: Tue, 3 Sep 2019 22:36:33 -0600 [thread overview]
Message-ID: <20190904043633.65026-1-skunberg.kelsey@gmail.com> (raw)
Patch 1: Change pci_device_is_present() name to pci_dev_is_inaccessible()
to encourage only using to learn if we should not access a
device that's inaccessible. Return value will need to be reversed
to reflect the name change.
Patch 2: Relies on patch 1. Unify pci_dev_is_disconnected() with
pci_dev_is_inaccessible() so there is only one function
needed to learn if a device is inaccessible due to surprise
removal or an error condition.
Kelsey Skunberg (2):
PCI: Change pci_device_is_present() to pci_dev_is_inaccessible()
PCI: Unify pci_dev_is_disconnected() and pci_dev_is_inaccessible()
drivers/net/ethernet/broadcom/tg3.c | 4 ++--
drivers/net/ethernet/intel/igb/igb_main.c | 2 +-
drivers/nvme/host/pci.c | 2 +-
drivers/pci/access.c | 12 ++++++------
drivers/pci/hotplug/acpiphp_glue.c | 2 +-
drivers/pci/msi.c | 4 ++--
drivers/pci/pci.c | 12 ++++++------
drivers/pci/pci.h | 5 -----
drivers/pci/pcie/portdrv_core.c | 2 +-
drivers/thunderbolt/nhi.c | 2 +-
include/linux/pci.h | 2 +-
11 files changed, 22 insertions(+), 27 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-04 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 4:36 Kelsey Skunberg [this message]
2019-09-04 4:36 ` [PATCH 1/2] PCI: Change pci_device_is_present() to pci_dev_is_inaccessible() Kelsey Skunberg
2019-09-04 4:36 ` [PATCH 2/2] PCI: Unify pci_dev_is_disconnected() and pci_dev_is_inaccessible() Kelsey Skunberg
2019-09-04 5:35 ` Lukas Wunner
2019-09-04 18:45 ` Bjorn Helgaas
2019-09-05 6:43 ` Kelsey Skunberg
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=20190904043633.65026-1-skunberg.kelsey@gmail.com \
--to=skunberg.kelsey@gmail.com \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=skhan@linuxfoundation.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).