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
| ||
|
Message-ID: <CAE9FiQV16BO-gC7Etm93OOG3tVY1Av614jZoZb_8cHeZ3oUq8A@mail.gmail.com> Date: Tue, 18 Dec 2012 17:57:20 -0800 From: Yinghai Lu <yinghai@...nel.org> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Toshi Kani <toshi.kani@...com>, ACPI Devel Maling List <linux-acpi@...r.kernel.org>, Bjorn Helgaas <bhelgaas@...gle.com>, LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org, Myron Stowe <myron.stowe@...hat.com>, Yijing Wang <wangyijing0307@...il.com>, Jiang Liu <liuj97@...il.com> Subject: Re: [PATCH rev.2 1/6] ACPI: Separate adding ACPI device objects from probing ACPI drivers On Tue, Dec 18, 2012 at 2:05 PM, Rafael J. Wysocki <rjw@...k.pl> wrote: >> >> i think we should put jiang four patches before Rafael's patches. >> >> http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=shortlog;h=refs/heads/for-pci-jiang-hotplug > > Actually, I have something more radical than that in mind. :-) > > Namely, we don't need to call the wakeup-related stuff from acpi_pci_bind() and > acpi_pci_unbind(). It's only there, because I did't find a better place for it > when I added it. > > If we can set the ACPI handles of PCI devices in pci_scan_device(), which isn't > too difficult to do (I actually have a patch for that and it's not too invasive), > we can easily move the wakeup enabling stuff to pci_pm_init() and wakeup > disabling somewhere near pci_release_capabilities(). good, let's see how acpi handles could be be passed to pci devices. Yinghai -- 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