rcu: Enable DEBUG_OBJECTS_RCU_HEAD from !PREEMPT

[deliverable/linux.git] / Documentation / development-process / 7.AdvancedTopics

diff --git a/Documentation/development-process/7.AdvancedTopics b/Documentation/development-process/7.AdvancedTopics
index 837179447e17f0e423d5b2e5f2bc54eb04bde3db..26dc3fa196e46fc9a1f8ef9f03e303c409e5b8b2 100644 (file)
--- a/Documentation/development-process/7.AdvancedTopics
+++ b/Documentation/development-process/7.AdvancedTopics
@@ -119,7 +119,7 @@ can affect your ability to get trees pulled in the future.  Quoting Linus:
        to trust things *without* then having to go and check every
        individual change by hand.
 
        to trust things *without* then having to go and check every
        individual change by hand.
 

-(http://lwn.net/Articles/224135/).  
+(http://lwn.net/Articles/224135/).

 
 To avoid this kind of situation, ensure that all patches within a given
 branch stick closely to the associated topic; a "driver fixes" branch
 
 To avoid this kind of situation, ensure that all patches within a given
 branch stick closely to the associated topic; a "driver fixes" branch


@@ -138,7 +138,7 @@ When requesting a pull, be sure to give all the relevant information: where
 your tree is, what branch to pull, and what changes will result from the
 pull.  The git request-pull command can be helpful in this regard; it will
 format the request as other developers expect, and will also check to be
 your tree is, what branch to pull, and what changes will result from the
 pull.  The git request-pull command can be helpful in this regard; it will
 format the request as other developers expect, and will also check to be

-sure that you have remembered to push those changes to the public server. 
+sure that you have remembered to push those changes to the public server.

 
 
 7.2: REVIEWING PATCHES
 
 
 7.2: REVIEWING PATCHES