Re: [PATCH] 2.6.22 - Documentation Cleanup

["Jesper Juhl" <jesper.juhl@gmail.com>]

On 12/07/07, Matt LaPlante <kernel1@cyberdogtech.com> wrote:
> Version 2 with fixes suggested by Randy & Joe.
>
> On Mon, 9 Jul 2007 13:45:16 -0400
> Matt LaPlante <kernel1@cyberdogtech.com> wrote:
>
> > Fix misc small issues/typos/grammar in Documentation txts for 2.6.22.
> >

Looks good to me, except for a few minor bits outlined below.


> > Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
> > --
>
> diff -ru a/Documentation/arm/Samsung-S3C24XX/DMA.txt b/Documentation/arm/Samsung-S3C24XX/DMA.txt
> --- a/Documentation/arm/Samsung-S3C24XX/DMA.txt 2007-07-08 19:32:17.000000000 -0400
> +++ b/Documentation/arm/Samsung-S3C24XX/DMA.txt 2007-07-11 21:47:43.000000000 -0400
[snip]
>
>     struct s3c24xx_dma_order has a list of channels, and
> -   each channel within has a slot for a list of dma
> -   channel numbers. The slots are searched in order, for
> -   the presence of a dma channel number with DMA_CH_VALID
> +   each channel within has a slot for a list of DMA
> +   channel numbers. The slots are searched in order for
> +   the presence of a DMA channel number with DMA_CH_VALID
>     orred in.

"orred"?? Wouldn't "OR'ed" or similar be better?

[snip]
>
>  ** WARNING **
> -I may not be held responsible for any dammage or harm caused if you try to
> +I may not be held responsible for any damage or harm caused if you try to

I'm guessing that the original author really meant to write "I shall
not be held responsible ..."

[snip]
>
>  This is a symlink to the latest version, which at the time of writing is
>  20061214, the only release of kexec-tools-testing so far. As other versions
> -are made released, the older onese will remain available at
> +are made released, the older ones will remain available at

s/are made released/are released/

[snip]
> @@ -1172,7 +1172,7 @@
>         recommended version is 3.2 or later. Here, the F/W support is in
>         a stable and reliable condition. Wide-addressing is in addition
>         supported.
> -     Q: I get a Ooops message and something like "killing interrupt".
> +     Q: I get a oops message and something like "killing interrupt".

I believe that should be "Oops" - two o's, first one uppercase.

[snip]
>
> -   If you have extensive bugreports, including Ooops messages and
> +   If you have extensive bug reports, including oops messages and

"Oops" ?

[snip]
> @@ -10,10 +10,11 @@
>      cpu. This is not ideal and leads to code duplication i.e. Linux now has 4

s/cpu/CPU/ ?

[snip]


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html