On Wed, Mar 28, 2012 at 05:07:03PM +0530, Thomas Abraham wrote: > On 28 March 2012 17:04, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Right, this does seem like something which it'd be better to handle > > more gracefully in the PM core. > Ok. Selecting PM_GENERIC_DOMAINS without checking for dependency on PM > did not seem correct. I dunno, perhaps the PM guys will disagree but it seems like if the idiomatic way to use this is to select it the API ought to cope with being selected when half enabled. As I've said before I'm in favour of just making CONFIG_PM non-optional, I'm not convinced there's much meaningful use case for disabling it.
Attachment:
signature.asc
Description: Digital signature
