summaryrefslogtreecommitdiffstats
path: root/drivers/pci/msi.c
diff options
context:
space:
mode:
authorStephen M. Cameron <scameron@beardog.cce.hp.com>2013-11-01 14:34:55 -0500
committerBjorn Helgaas <bhelgaas@google.com>2013-11-06 16:08:17 -0700
commitf92d74c1f5afaff7cd1ea14ade8f1ba6b519e422 (patch)
tree406dec41eebbb8f241bef2437e9c5765e65e45e6 /drivers/pci/msi.c
parentfbeeb822f6f45cadf154d7b7cff1c13537cd799d (diff)
downloadop-kernel-dev-f92d74c1f5afaff7cd1ea14ade8f1ba6b519e422.zip
op-kernel-dev-f92d74c1f5afaff7cd1ea14ade8f1ba6b519e422.tar.gz
PCI: Warn on driver probe return value greater than zero
Ages ago, drivers could return values greater than zero from their probe function and this would be regarded as success. But after f3ec4f87d607 ("PCI: change device runtime PM settings for probe and remove") and 967577b06241 ("PCI/PM: Keep runtime PM enabled for unbound PCI devices"), we set dev->driver to NULL if the driver's probe function returns a value greater than zero. __pci_device_probe() treats this as success, and drivers can still mostly work even with dev->driver == NULL, but PCI power management doesn't work, and we don't call the driver's remove function on rmmod. To help catch these driver problems, issue a warning in this case. [bhelgaas: changelog] Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'drivers/pci/msi.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud