Re: [linux-pm] [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface

Hi!

> Fix the per-device state file to respect the actual state that
> is reported by the device, or written to the file.

Can we let "state" file die? You actually suggested that at one point.

I do not think passing states in u32 is good idea. New interface that passes
state as string would probably be better.

				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 3/5] [pm] Respect the actual device power states in sysfs interface
  - From: Patrick Mochel <[email protected]>

References:
- [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface
  - From: Patrick Mochel <[email protected]>

Prev by Date: Re: [linux-pm] [PATCH 2/5] [pm] Add state field to pm_message_t (to hold actual state device is in)
Next by Date: Re: Which is simpler? (Was Re: [Suspend2-devel] Re: [ 00/10] [Suspend2] Modules support.)
Previous by thread: [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface
Next by thread: Re: [linux-pm] [PATCH 3/5] [pm] Respect the actual device power states in sysfs interface
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]