From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI: Remove service driver load/unload messages
Date: Thu, 17 Nov 2016 14:40:42 +0100 [thread overview]
Message-ID: <20161117134042.GA11658@wunner.de> (raw)
In-Reply-To: <20161116221310.15842.25671.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Wed, Nov 16, 2016 at 04:13:10PM -0600, Bjorn Helgaas wrote:
> Remove the "service driver %s loaded" and unloaded messages. I don't think
> these add any useful information.
I think those particular ones have a value to some extent because
they communicate for which of the port's capabilities a driver is
available and loaded. For ports below a hotplug port they also
comunicate the steps to unbind the ports from their drivers when
the device is unplugged.
E.g. when I plug in the Apple Thunderbolt Ethernet adapter I get this
because a new hotplug port appears below the hotplug port of the host
controller:
[ 141.926865] pciehp 0000:0a:00.0:pcie204: service driver pciehp loaded
On unplug I get this:
[ 202.497548] pciehp 0000:0a:00.0:pcie204: unloading service driver pciehp
Thanks,
Lukas
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> drivers/pci/pcie/portdrv_core.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
> index e9270b4..9698289 100644
> --- a/drivers/pci/pcie/portdrv_core.c
> +++ b/drivers/pci/pcie/portdrv_core.c
> @@ -499,7 +499,6 @@ static int pcie_port_probe_service(struct device *dev)
> if (status)
> return status;
>
> - dev_printk(KERN_DEBUG, dev, "service driver %s loaded\n", driver->name);
> get_device(dev);
> return 0;
> }
> @@ -524,8 +523,6 @@ static int pcie_port_remove_service(struct device *dev)
> pciedev = to_pcie_device(dev);
> driver = to_service_driver(dev->driver);
> if (driver && driver->remove) {
> - dev_printk(KERN_DEBUG, dev, "unloading service driver %s\n",
> - driver->name);
> driver->remove(pciedev);
> put_device(dev);
> }
>
next prev parent reply other threads:[~2016-11-17 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:13 [PATCH 0/4] PCI: Tidy up messages Bjorn Helgaas
2016-11-16 22:13 ` [PATCH 1/4] PCI: Remove service driver load/unload messages Bjorn Helgaas
2016-11-17 13:40 ` Lukas Wunner [this message]
2016-11-17 20:49 ` Bjorn Helgaas
2016-11-18 10:00 ` Lukas Wunner
2016-11-18 14:45 ` Bjorn Helgaas
2016-11-16 22:13 ` [PATCH 2/4] PCI: hotplug: Remove hotplug core message Bjorn Helgaas
2016-11-16 22:13 ` [PATCH 3/4] PCI: pciehp: Remove loading message Bjorn Helgaas
2016-11-16 22:13 ` [PATCH 4/4] PCI: Expand "VPD access disabled" quirk message Bjorn Helgaas
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=20161117134042.GA11658@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.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).