Please Pavel, no ! We are still discussing some of the details of the message formats, and what we are coming up with definitely does NOT look like hwat you are proposing here. Stop just producing patches like that all the time that are more confusing than anything else. I could do that too, and it would be useless... More specifically, this list: +#define PMSG_APM_SUSPEND ((__force pm_message_t) 3) +#define PMSG_APM_STANDBY ((__force pm_message_t) 3) +#define PMSG_SYSTEM_HALT ((__force pm_message_t) 3) +#define PMSG_SYSTEM_REBOOT ((__force pm_message_t) 3) +#define PMSG_SYSTEM_SHUTDOWN ((__force pm_message_t) 3) +#define PMSG_SUSPEND_RAM ((__force pm_message_t) 3) +#define PMSG_SUSPEND_DISK ((__force pm_message_t) 3) +#define PMSG_DEV_DETACH ((__force pm_message_t) 3) +#define PMSG_ON ((__force pm_message_t) 0) Is just not useful at this point. We decided we would _NOT_ pass the system state down to devices (STD, STR, ...) but an abstract FREEZE/IDLE/SUSPEND message, where is that reflected in the above ? Ben.
