summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/chips
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2012-02-15 11:48:34 +0000
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-27 00:36:40 +0100
commit342d3a93e2b191b0ada07ba7c48380181c9214e8 (patch)
tree300816865f5d73a345813f4095647c920a6f3b50 /drivers/mtd/chips
parent492b8bde2c2badd3e5845f2e8de6fa9065438743 (diff)
downloadtalos-op-linux-342d3a93e2b191b0ada07ba7c48380181c9214e8.tar.gz
talos-op-linux-342d3a93e2b191b0ada07ba7c48380181c9214e8.zip
mtd: fix 'Flash device refused suspend due to active operation' message
While debugging on SA11x0, the following message was observed: "Flash device refused suspend due to active operation (state 20)" Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers/mtd/chips')
-rw-r--r--drivers/mtd/chips/cfi_cmdset_0001.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mtd/chips/cfi_cmdset_0001.c b/drivers/mtd/chips/cfi_cmdset_0001.c
index 2d9669047ed4..920b474a5613 100644
--- a/drivers/mtd/chips/cfi_cmdset_0001.c
+++ b/drivers/mtd/chips/cfi_cmdset_0001.c
@@ -2479,7 +2479,7 @@ static int cfi_intelext_suspend(struct mtd_info *mtd)
allowed to. Or should we return -EAGAIN, because the upper layers
ought to have already shut down anything which was using the device
anyway? The latter for now. */
- printk(KERN_NOTICE "Flash device refused suspend due to active operation (state %d)\n", chip->oldstate);
+ printk(KERN_NOTICE "Flash device refused suspend due to active operation (state %d)\n", chip->state);
ret = -EAGAIN;
case FL_PM_SUSPENDED:
break;
OpenPOWER on IntegriCloud