Tejun Heo wrote:
When no reset method is available, libata currently oopses. Although the condition can't happen unless there's a bug in a low level driver, oopsing isn't the best way to report the error condition. Complain, dump stack and fail reset instead. Signed-off-by: Tejun Heo <htejun@xxxxxxxxx> --- This patch is on top of upstream (a984f58dd97f22f5113700322fed311a0ee29947) + prefer-hardreset patchset http://thread.gmane.org/gmane.linux.ide/27447 drivers/ata/libata-eh.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-)
applied -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
