Re: [PATCH] Documentation: remove duplicate cleanups

[jensmh@gmx.de]

Paolo Ornati writes:

> diff --git a/Documentation/block/as-iosched.txt b/Documentation/block/as-iosched.txt
> index 6f47332..ed24cdd 100644
> --- a/Documentation/block/as-iosched.txt
> +++ b/Documentation/block/as-iosched.txt
> @@ -111,7 +111,7 @@ or if the next request in the queue is "
>  just completed request, it is dispatched immediately.  Otherwise,
>  statistics (average think time, average seek distance) on the process
>  that submitted the just completed request are examined.  If it seems
> -likely that that process will submit another request soon, and that

old version is correct, I think.

> +likely that process will submit another request soon, and that
>  request is likely to be near the just completed request, then the IO
>  scheduler will stop dispatching more read requests for up time (antic_expire)
>  milliseconds, hoping that process will submit a new request near the one


> diff --git a/Documentation/exception.txt b/Documentation/exception.txt
> index 3cb39ad..75aaa6e 100644
> --- a/Documentation/exception.txt
> +++ b/Documentation/exception.txt
> @@ -10,7 +10,7 @@ int verify_area(int type, const void * a
>  function (which has since been replaced by access_ok()).
>  
>  This function verified that the memory area starting at address 
> -addr and of size size was accessible for the operation specified 

maybe old version is correct.

> +addr and of size was accessible for the operation specified
>  in type (read or write). To do this, verify_read had to look up the 
>  virtual memory area (vma) that contained the address addr. In the 
>  normal case (correctly working program), this test was successful. 
> diff --git a/Documentation/fb/fbcon.txt b/Documentation/fb/fbcon.txt
> index f373df1..4a9739a 100644
> --- a/Documentation/fb/fbcon.txt
> +++ b/Documentation/fb/fbcon.txt
> @@ -150,7 +150,7 @@ C. Boot options
>  
>  C. Attaching, Detaching and Unloading
>  
> -Before going on on how to attach, detach and unload the framebuffer console, an

not sure here, I'm not a native english speaker.

> +Before going on how to attach, detach and unload the framebuffer console, an
>  illustration of the dependencies may help.
>