aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/rtc
diff options
context:
space:
mode:
authorRafael J. Wysocki <rjw@sisk.pl>2007-06-17 19:50:51 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2007-07-11 16:09:02 -0700
commit43a49f8baa6b0e7e5b68ed0ee141e1efacfd9ae6 (patch)
tree2759e89c277a3fa9dcb4d5787375356fad29ecc7 /drivers/rtc
parent1c3f7d1c79425dd8f627b8da139fd1855f096b6e (diff)
downloadkernel_samsung_aries-43a49f8baa6b0e7e5b68ed0ee141e1efacfd9ae6.zip
kernel_samsung_aries-43a49f8baa6b0e7e5b68ed0ee141e1efacfd9ae6.tar.gz
kernel_samsung_aries-43a49f8baa6b0e7e5b68ed0ee141e1efacfd9ae6.tar.bz2
PM: Do not check parent state in suspend and resume core code
The checks if the device's parent is in the right state done in drivers/base/power/suspend.c and drivers/base/power/resume.c serve no particular purpose, since if the parent is in a wrong power state, the device's suspend or resume callbacks are supposed to return an error anyway. Moreover, they are also useless from the sanity checking point of view, because they rely on the code being checked to set dev->parent->power.power_state.event appropriately, which need not happen if that code is buggy. For these reasons they can be removed. Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl> Acked-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/rtc')
0 files changed, 0 insertions, 0 deletions