X-Git-Url: http://git.samba.org/samba.git/?a=blobdiff_plain;f=Documentation%2FRCU%2FUP.txt;h=53bde717017bb8cde0fbec21f0dd65db33db2f91;hb=4fea6ef0b219d66b8a901fea1744745a1ed2f79b;hp=90ec5341ee981a0a397710d2ffd1261eb2557896;hpb=eae6fa9b0c3e2cb49cc157e906dd0ac52cfd7ca5;p=sfrench%2Fcifs-2.6.git

diff --git a/Documentation/RCU/UP.txt b/Documentation/RCU/UP.txt
index 90ec5341ee98..53bde717017b 100644
--- a/Documentation/RCU/UP.txt
+++ b/Documentation/RCU/UP.txt
@@ -86,10 +86,8 @@ even on a UP system.  So do not do it!  Even on a UP system, the RCU
 infrastructure -must- respect grace periods, and -must- invoke callbacks
 from a known environment in which no locks are held.
 
-It -is- safe for synchronize_sched() and synchronize_rcu_bh() to return
-immediately on an UP system.  It is also safe for synchronize_rcu()
-to return immediately on UP systems, except when running preemptable
-RCU.
+Note that it -is- safe for synchronize_rcu() to return immediately on
+UP systems, including !PREEMPT SMP builds running on UP systems.
 
 Quick Quiz #3: Why can't synchronize_rcu() return immediately on
 	UP systems running preemptable RCU?