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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 11 Aug 2014 08:15:22 -0700
From:	Olof Johansson <>
To:	"Rafael J. Wysocki" <>
Cc:	Linux PM list <>,
	Linux Kernel Mailing List <>,
	Pavel Machek <>, Zhang Rui <>,
	Stephen Rothwell <>
Subject: Re: [RFC][PATCH] PM / sleep: Rename symbols, functions and variables
 related to sleep

On Sun, Jul 27, 2014 at 4:13 PM, Rafael J. Wysocki <> wrote:
> From: Rafael J. Wysocki <>
> The names of several symbols, data types, functions and variables
> related to system sleep states are confusing and don't reflect the
> real behavior of those states correctly.
> First of all, there generally are two sleep states that require
> platform support and one sleep state that is platform-independent.
> The first two of them are currently known as MEM and STANDBY,
> although these names really only match what the states do on full
> hardware ACPI compliant systems.  MEM in particular is supposed
> to mean "suspend-to-RAM", but in fact it means "the deepest sleep
> state available with platform support".  The definition of STANDBY
> is even more arbitrary.
> Moreover, the remaining sleep state that doesn't need platform support
> is currently called FREEZE, which leads to double confusion with the
> process freezer (used during transitions to all sleep states) and
> with the freeze stage of processing devices during hibernation.
> For these reasons, rename the PM_SUSPEND_MEM, PM_SUSPEND_STANDBY
> everywhere and rename data types, functions and variables related to
> those states to match the new names of the symbols.
> This is a semi-mechanical replacement of names and it should not lead
> to any functional differences.
> Signed-off-by: Rafael J. Wysocki <>

This showed up in -next over this weekend and broke two ARM builds.
Please don't add new code to -next during a merge window.


/home/build/work/batch/arch/arm/mach-s5pv210/pm.c:150:12: error:
'suspend_valid_only_mem' undeclared here (not in a function)
  .valid  = suspend_valid_only_mem,

/home/build/work/batch/arch/arm/mach-mmp/pm-pxa910.c: In function
/home/build/work/batch/arch/arm/mach-mmp/pm-pxa910.c:243:65: error:
expected ')' before ';' token
  return state == PM_SUSPEND_SHALLOW || (state == PM_SUSPEND_DEEP;
/home/build/work/batch/arch/arm/mach-mmp/pm-pxa910.c:244:1: error:
expected ';' before '}' token

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists