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 <[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 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 - 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/
