Re: Policy question (was Re: [2.6.12-rc1][ACPI][suspend] /proc/acpi/sleep vs /sys/power/state issue - 'standby' on a laptop)

Well, of course. When I get around to figuring out the best way to do this. Since I don't want to bloat up sysfs ACPI stuff just to check if the echoed value is a number or string. We can just gradually phase it out by just marking it DEPRECATED and keep it ON in the Kbuild file so nobody

Policy question (was Re: [2.6.12-rc1][ACPI][suspend] /proc/acpi/sleep vs /sys/power/state issue - 'standby' on a laptop)

On Wednesday 06 April 2005 05:22 pm, Shawn Starr wrote: > --- Pavel Machek <[EMAIL PROTECTED]> wrote: > > Hi! > > > > > So nobody minds if I make this into a CONFIG > > > > option marked as Deprecated? :) > > > > Actually it should probably go through > > > >

Policy question (was Re: [2.6.12-rc1][ACPI][suspend] /proc/acpi/sleep vs /sys/power/state issue - 'standby' on a laptop)

On Wednesday 06 April 2005 05:22 pm, Shawn Starr wrote: --- Pavel Machek [EMAIL PROTECTED] wrote: Hi! So nobody minds if I make this into a CONFIG option marked as Deprecated? :) Actually it should probably go through Documentation/feature-removal-schedule.txt ...and give

Re: Policy question (was Re: [2.6.12-rc1][ACPI][suspend] /proc/acpi/sleep vs /sys/power/state issue - 'standby' on a laptop)

Well, of course. When I get around to figuring out the best way to do this. Since I don't want to bloat up sysfs ACPI stuff just to check if the echoed value is a number or string. We can just gradually phase it out by just marking it DEPRECATED and keep it ON in the Kbuild file so nobody