aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/power
diff options
context:
space:
mode:
authorAdrian Bunk <bunk@stusta.de>2006-01-09 18:08:17 -0500
committerAdrian Bunk <bunk@r063144.stusta.swh.mhn.de>2006-01-09 18:08:17 -0500
commita58a414fd5438f5ade6210ad0e8b14fbd6f503c5 (patch)
tree89c934be5760d7e26aadf88e90cb954e80591f9e /Documentation/power
parentf17578decc40df8fceff82b106582e30bdfb3189 (diff)
spelling: s/usefull/useful/
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/power')
-rw-r--r--Documentation/power/swsusp.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
index cd0fcd89a6f0..08c79d4dc540 100644
--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -212,7 +212,7 @@ A: Try running
212 212
213cat `cat /proc/[0-9]*/maps | grep / | sed 's:.* /:/:' | sort -u` > /dev/null 213cat `cat /proc/[0-9]*/maps | grep / | sed 's:.* /:/:' | sort -u` > /dev/null
214 214
215after resume. swapoff -a; swapon -a may also be usefull. 215after resume. swapoff -a; swapon -a may also be useful.
216 216
217Q: What happens to devices during swsusp? They seem to be resumed 217Q: What happens to devices during swsusp? They seem to be resumed
218during system suspend? 218during system suspend?
@@ -323,7 +323,7 @@ to be useless to try to suspend to disk while that app is running?
323A: No, it should work okay, as long as your app does not mlock() 323A: No, it should work okay, as long as your app does not mlock()
324it. Just prepare big enough swap partition. 324it. Just prepare big enough swap partition.
325 325
326Q: What information is usefull for debugging suspend-to-disk problems? 326Q: What information is useful for debugging suspend-to-disk problems?
327 327
328A: Well, last messages on the screen are always useful. If something 328A: Well, last messages on the screen are always useful. If something
329is broken, it is usually some kernel driver, therefore trying with as 329is broken, it is usually some kernel driver, therefore trying with as