X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=Documentation%2Fdevelopment-process%2F4.Coding;h=a5a3450faaa0dcdbb990fcc27d0bf68765f56bb9;hb=c7121843685de2bf7f3afd3ae1d6a146010bf1fc;hp=014aca8f14e2a52294dfdf63eaa33bd5bb8d5ee6;hpb=55fa518867978e1f5fd8353098f80d125ac734d7;p=mv-sheeva.git

diff --git a/Documentation/development-process/4.Coding b/Documentation/development-process/4.Coding
index 014aca8f14e..a5a3450faaa 100644
--- a/Documentation/development-process/4.Coding
+++ b/Documentation/development-process/4.Coding
@@ -375,10 +375,10 @@ say, this can be a large job, so it is best to be sure that the
 justification is solid.
 
 When making an incompatible API change, one should, whenever possible,
-ensure that code which has not been updated is caught by the compiler.  
+ensure that code which has not been updated is caught by the compiler.
 This will help you to be sure that you have found all in-tree uses of that
 interface.  It will also alert developers of out-of-tree code that there is
 a change that they need to respond to.  Supporting out-of-tree code is not
 something that kernel developers need to be worried about, but we also do
-not have to make life harder for out-of-tree developers than it it needs to
-be. 
+not have to make life harder for out-of-tree developers than it needs to
+be.