summaryrefslogtreecommitdiffstats
path: root/drivers/ata
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2011-07-01 15:12:09 +0200
committerJeff Garzik <jgarzik@pobox.com>2011-07-23 18:02:51 -0400
commit38941c9521e9ee6064b402dd460ac9dd2df89890 (patch)
tree57c45c14219b5707f33624655faa77566574ac33 /drivers/ata
parent345347c5d767332d7352f220808fe9b5e4af8c6b (diff)
downloadop-kernel-dev-38941c9521e9ee6064b402dd460ac9dd2df89890.zip
op-kernel-dev-38941c9521e9ee6064b402dd460ac9dd2df89890.tar.gz
libata: report link resume failure as KERN_WARNING instead of ERR
Link resume failure in itself isn't an error condition and may happen regularly depending on hardware configuration. Reporting it as KERN_ERR makes the condition unnecessarily prominent (e.g. reported during boot). Use KERN_WARNING instead. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: David Shaw <dshaw@jabberwocky.com> Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
Diffstat (limited to 'drivers/ata')
-rw-r--r--drivers/ata/libata-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 83a2929..4a3a5ae 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -3534,7 +3534,7 @@ int sata_link_resume(struct ata_link *link, const unsigned long *params,
} while ((scontrol & 0xf0f) != 0x300 && --tries);
if ((scontrol & 0xf0f) != 0x300) {
- ata_link_err(link, "failed to resume link (SControl %X)\n",
+ ata_link_warn(link, "failed to resume link (SControl %X)\n",
scontrol);
return 0;
}
OpenPOWER on IntegriCloud