From 7c3e3076cf95f5ed1c199fb24378511110516dd6 Mon Sep 17 00:00:00 2001
From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Sun, 6 Nov 2011 22:00:20 +0100
Subject: [PATCH] --- yaml --- r: 275159 b: refs/heads/master c:
 5f11161675be1351cadb96c83850e20bf5bcdc48 h: refs/heads/master i:   275157:
 a50c48f80b1d8964d60990bcafbdea9adf20053f   275155:
 5cea553c398aa83f4d2b2944275c3a964c162e3e   275151:
 b4178b7c5e0396921f2d403972e5ad061f1441a8 v: v3

---
 [refs]                                            | 2 +-
 trunk/Documentation/cgroups/freezer-subsystem.txt | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/[refs] b/[refs]
index e8d3526ccaa9..4b3015424daa 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: a6f05b97d1ba87326bd96f3da9fef994830d6994
+refs/heads/master: 5f11161675be1351cadb96c83850e20bf5bcdc48
diff --git a/trunk/Documentation/cgroups/freezer-subsystem.txt b/trunk/Documentation/cgroups/freezer-subsystem.txt
index c21d77742a07..7e62de1e59ff 100644
--- a/trunk/Documentation/cgroups/freezer-subsystem.txt
+++ b/trunk/Documentation/cgroups/freezer-subsystem.txt
@@ -33,9 +33,9 @@ demonstrate this problem using nested bash shells:
 
 	From a second, unrelated bash shell:
 	$ kill -SIGSTOP 16690
-	$ kill -SIGCONT 16990
+	$ kill -SIGCONT 16690
 
-	<at this point 16990 exits and causes 16644 to exit too>
+	<at this point 16690 exits and causes 16644 to exit too>
 
 This happens because bash can observe both signals and choose how it
 responds to them.