Skip to contentSkip to conversation

Documentation: Fix typo in freezer-subsystem.txt

PATCH In review Rafael J. Wysocki 3 participants 4 messages Nov 6, 2011 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Documentation: Fix typo in freezer-subsystem.txt

From: Rafael J. Wysocki <[email protected]>

Fix a typo in Documentation/cgroups/freezer-subsystem.txt.

---
 Documentation/cgroups/freezer-subsystem.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/cgroups/freezer-subsystem.txt +2 -2
Index: linux-3.0-SLE11-SP2/Documentation/cgroups/freezer-subsystem.txt
===================================================================
@@ -33,9 +33,9 @@ demonstrate this problem using nested ba
 
 	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.
Reviewed-by on v1 1/1
#1 lore raw
Quoted 6 lines · Rafael J. Wysocki

From: Rafael J. Wysocki <[email protected]>

Fix a typo in Documentation/cgroups/freezer-subsystem.txt.

---

Thanks,
Srivatsa S. Bhat

Quoted 24 lines
 Documentation/cgroups/freezer-subsystem.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: linux-3.0-SLE11-SP2/Documentation/cgroups/freezer-subsystem.txt
===================================================================

Documentation/cgroups/freezer-subsystem.txt +2 -3
@@ -33,9 +33,9 @@ demonstrate this problem using nested ba
 
 	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.
--

To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Acked-by on v1 1/1
#2 lore raw
In reply to Rafael J. Wysocki
Quoted 5 lines · Rafael J. Wysocki

From: Rafael J. Wysocki <[email protected]>

Fix a typo in Documentation/cgroups/freezer-subsystem.txt.

You are welcome to merge this with PM patches.. or did you want me to merge it?

Quoted 21 lines
---
 Documentation/cgroups/freezer-subsystem.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: linux-3.0-SLE11-SP2/Documentation/cgroups/freezer-subsystem.txt
===================================================================

Documentation/cgroups/freezer-subsystem.txt +2 -3
@@ -33,9 +33,9 @@ demonstrate this problem using nested ba
 
 	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.
--
Signature · 2 lines
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
#3 lore raw
Quoted 11 lines · Randy Dunlap
Quoted 5 lines · Rafael J. Wysocki

From: Rafael J. Wysocki <[email protected]>

Fix a typo in Documentation/cgroups/freezer-subsystem.txt.

You are welcome to merge this with PM patches.. or did you want me to merge it?

Well, I can do that. :-)

Thanks,
Rafael

Quoted 24 lines
Quoted 21 lines
---
 Documentation/cgroups/freezer-subsystem.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: linux-3.0-SLE11-SP2/Documentation/cgroups/freezer-subsystem.txt
===================================================================

Documentation/cgroups/freezer-subsystem.txt +2 -3
@@ -33,9 +33,9 @@ demonstrate this problem using nested ba
 
 	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.
--