Re: [PATCH v6 1/3] libata, libsas: kill pm_result and related cleanup

2014-03-18 Thread Tejun Heo
On Fri, Mar 14, 2014 at 01:52:48PM -0700, Dan Williams wrote: Tejun says: At least for libata, worrying about suspend/resume failures don't make whole lot of sense. If suspend failed, just proceed with suspend. If the device can't be woken up afterwards, that's that. There isn't

Re: [PATCH v6 1/3] libata, libsas: kill pm_result and related cleanup

2014-03-18 Thread Dan Williams
On Tue, Mar 18, 2014 at 9:03 AM, Tejun Heo t...@kernel.org wrote: On Fri, Mar 14, 2014 at 01:52:48PM -0700, Dan Williams wrote: Tejun says: At least for libata, worrying about suspend/resume failures don't make whole lot of sense. If suspend failed, just proceed with suspend. If the

Re: [PATCH v6 1/3] libata, libsas: kill pm_result and related cleanup

2014-03-18 Thread Tejun Heo
On Fri, Mar 14, 2014 at 01:52:48PM -0700, Dan Williams wrote: Tejun says: At least for libata, worrying about suspend/resume failures don't make whole lot of sense. If suspend failed, just proceed with suspend. If the device can't be woken up afterwards, that's that. There isn't

[PATCH v6 1/3] libata, libsas: kill pm_result and related cleanup

2014-03-14 Thread Dan Williams
Tejun says: At least for libata, worrying about suspend/resume failures don't make whole lot of sense. If suspend failed, just proceed with suspend. If the device can't be woken up afterwards, that's that. There isn't anything we could have done differently anyway. The same for