| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 3 Feb 2015 17:55:25 +0800 From: Ken Xue <Ken.Xue@....com> To: "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com> CC: "Rafael J. Wysocki" <rjw@...ysocki.net>, "andy.shevchenko@...il.com" <andy.shevchenko@...il.com>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH V2] acpi:apd:add AMD ACPI2Platform device support for x86 system. On Tue, 2015-02-03 at 11:53 +0200, mika.westerberg@...ux.intel.com wrote: > On Tue, Feb 03, 2015 at 09:04:55AM +0800, Ken Xue wrote: > > as you said, platform_drv_probe calls dev_pm_domain_attach(). but > > platform_drv_probe just is a default probe routine. Not all platform > > device drivers use this probe routine. so, codes here may be still > > necessary. > > Are you saying that for platform devices there is some other path to get > a driver probed, other than platform_drv_probe()? Can you point me to > it? >From the codes, i can see there is a possibility that drv->driver.probe may not be set in __platform_driver_register. But i really can not point out a use case that platform device driver without probe. so, it is safe to remove "dev_pm_domain_attach" in "acpi_apd_platform_notify". right? -- 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