On Wednesday 13 June 2007, Dmitry Torokhov wrote: > On Wednesday 13 June 2007 18:20, Kay Sievers wrote: > > Dmitry, you added this recently, is this used in any code you plan to > > merge soon? > > > > Yes, I will need it to implement input device resume (mainly to restore LED > state and repeat rate for keyboards). Why wouldn't that use the class device suspend/resume mechanism? - 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: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
- From: "Dmitry Torokhov" <[email protected]>
- Re: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
- References:
- [PATCH -mm 0/7] PM: Remove unused and unnecessary features from suspend and resume core
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
- From: "Kay Sievers" <[email protected]>
- Re: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
- From: Dmitry Torokhov <[email protected]>
- [PATCH -mm 0/7] PM: Remove unused and unnecessary features from suspend and resume core
- Prev by Date: Re: [patch] sched: fix SysRq-N (normalize RT tasks)
- Next by Date: Re: [2/2] 2.6.22-rc4: known regressions v3
- Previous by thread: [PATCH -mm 3/3] PM: Do not check parent state in suspend and resume core code
- Next by thread: Re: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
- Index(es):
 |