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: Sat, 29 Nov 2014 01:52:32 +0100 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Linux PM list <linux-pm@...r.kernel.org> Cc: Linux PCI <linux-pci@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, ACPI Devel Maling List <linux-acpi@...r.kernel.org>, Alan Stern <stern@...land.harvard.edu>, Bjorn Helgaas <bhelgaas@...gle.com>, Kevin Hilman <khilman@...nel.org>, Ulf Hansson <ulf.hansson@...aro.org>, Geert Uytterhoeven <geert@...ux-m68k.org> Subject: Re: [Replacement][PATCH 1/4] PM: Merge the SET*_RUNTIME_PM_OPS() macros On Thursday, November 27, 2014 11:05:41 PM Rafael J. Wysocki wrote: > From: Rafael J. Wysocki <rafael.j.wysocki@...el.com> > > The SET_PM_RUNTIME_PM_OPS() and SET_RUNTIME_PM_OPS() macros are > identical except that one of them is not empty for CONFIG_PM set, > while the other one is not empty for CONFIG_PM_RUNTIME set, > respectively. > > However, after commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if > PM_SLEEP is selected) PM_RUNTIME is always set if PM is set, so one > of these macros is now redundant. > > For this reason, replace SET_PM_RUNTIME_PM_OPS() with > SET_RUNTIME_PM_OPS() everywhere and redefine the SET_PM_RUNTIME_PM_OPS > symbol as SET_RUNTIME_PM_OPS in case new code is starting to use the > macro being removed here. It turns out that I need to defer this one, because it breaks builds for CONFIG_PM selected without CONFIG_PM_SLEEP or CONFIG_PM_RUNTIME (which is arguably invalid, but some defconfigs evidently do that). I need to fix those defconfigs first. -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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