Re: [linux-pm] [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)

Hi!


> diff --git a/include/linux/pm.h b/include/linux/pm.h
> index 5be87ba..a7324ea 100644
> --- a/include/linux/pm.h
> +++ b/include/linux/pm.h
> @@ -140,6 +140,7 @@ struct device;
> 
>  typedef struct pm_message {
>  	int event;
> +	u32 state;
>  } pm_message_t;

We have had enough problems with u32s before... What about
char *, and pass real state names?
				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [linux-pm] [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
    • From: Patrick Mochel <[email protected]>
  • Re: [linux-pm] [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
    • From: Alan Stern <[email protected]>

• References:
  • [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
    • From: Patrick Mochel <[email protected]>

• Prev by Date: Re: [linux-pm] [PATCH 5/5] [pci pm] Make pci_choose_state() use the real device state requested
• Next by Date: Re: [linux-pm] [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface
• Previous by thread: Re: [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
• Next by thread: Re: [linux-pm] [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]