[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201111202331.00548.rjw@sisk.pl>
Date: Sun, 20 Nov 2011 23:31:00 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: David Fries <david@...es.net>
Cc: linux-kernel@...r.kernel.org,
Jesse Barnes <jbarnes@...tuousgeek.org>,
linux-pci@...r.kernel.org
Subject: Re: [PATH] pci_has_legacy_pm_support add driver and device to WARN
On Sunday, November 20, 2011, David Fries wrote:
> From: David Fries <David@...es.net>
>
> Include the driver name and device in warning when a pci driver
> supports both legacy pm and new framework as just the stack trace
> gives no way to identify the driver.
>
> Signed-off-by: David Fries <David@...es.net>
Acked-by: Rafael J. Wysocki <rjw@...k.pl>
> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>
> Cc: linux-pci@...r.kernel.org
> ---
> drivers/pci/pci-driver.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 12d1e81..3623d65 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -604,7 +604,8 @@ static bool pci_has_legacy_pm_support(struct pci_dev *pci_dev)
> * supported as well. Drivers are supposed to support either the
> * former, or the latter, but not both at the same time.
> */
> - WARN_ON(ret && drv->driver.pm);
> + WARN(ret && drv->driver.pm, "driver %s device %04x:%04x\n",
> + drv->name, pci_dev->vendor, pci_dev->device);
>
> return ret;
> }
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists