Re: [PATCH] Fix typos in doc and comments (1)

[Matt LaPlante <kernel1@cyberdogtech.com>]

On Mon, 16 Oct 2006 16:07:38 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:

> On Tue, 17 Oct 2006 00:50:56 +0200 (MEST) Jan Engelhardt wrote:
> 
> > 
> > 
> > Changes persistant -> persistent. www.dictionary.com does not know 
> > persistant (with an A), but should it be one of those things you can 
> > spell in more than one correct way, let me know.
> 
> I agree with it, but IIRC Alan said it could be either way.
> 

While I also agree, you're correct about Alan's claim.  He used a print dictionary...I've yet to find an online dictionary that supports this spelling.  (Note: I've found m-w.com to be the best at catching both British English and American English spellings.  Cambridge online is good too).

> > Index: linux-2.6.19-rc2/lib/textsearch.c
> > ===================================================================
> > --- linux-2.6.19-rc2.orig/lib/textsearch.c
> > +++ linux-2.6.19-rc2/lib/textsearch.c
> > @@ -40,7 +40,7 @@
> >   *       configuration according to the specified parameters.
> >   *   (3) User starts the search(es) by calling _find() or _next() to
> >   *       fetch subsequent occurrences. A state variable is provided
> > - *       to the algorihtm to store persistant variables.
> > + *       to the algorihtm to store persistent variables.
> 
> fix /algorithm/ while here?
> or did Matt already fix that one?
> 

I haven't yet submitted typo fixes to any c/h files, so no.  I actually do have a c/h file patch done and pending from a couple days ago, I just haven't mailed it yet.

> >   *   (4) Core eventually resets the search offset and forwards the find()
> >   *       request to the algorithm.
> >   *   (5) Algorithm calls get_next_block() provided by the user continously
> 
> ---
> ~Randy


-- 
Matt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/