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

[Shawn Starr <shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>]

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 looses the 
functionality until then.

I'm thinking 2 years but some say thats too long :)

Now that I look at it, I don't need to put it into a CONFIG option as its 
already a module :-) even better.

Shawn.

On April 11, 2005 20:09, Rob Landley wrote:
> On Wednesday 06 April 2005 05:22 pm, Shawn Starr wrote:
> > --- Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org> 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 it *long* timeout, since it is API
> > > change.
> > >          Pavel
>
> Shouldn't all deprecated features be in feature-removal-schedule.txt?
>
> There are four entries in feature-removal-schedule in 2.6.12-rc2, but
> `find . -name "Kconfig" | xargs grep -i deprecated` finds eight entries. 
> (And there's more if the grep -i is for "obsolete" instead...)
>
> Just wondering...
>
> Rob


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click