From: Randy Dunlap <rdunlap@xenotime.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: akpm@osdl.org, Matt LaPlante <kernel1@cyberdogtech.com>,
Linus Torvalds <torvalds@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix typos in doc and comments (1)
Date: Mon, 16 Oct 2006 16:07:38 -0700 [thread overview]
Message-ID: <20061016160738.2199bbcb.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0610170040510.30479@yvahk01.tjqt.qr>
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.
> 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?
> * (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
next prev parent reply other threads:[~2006-10-16 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 22:50 [PATCH] Fix typos in doc and comments (1) Jan Engelhardt
2006-10-16 23:00 ` [PATCH] Fix typos in doc and comments (2) Jan Engelhardt
2006-10-16 23:07 ` Randy Dunlap [this message]
2006-10-17 5:22 ` [PATCH] Fix typos in doc and comments (1) Matt LaPlante
2006-10-17 13:17 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061016160738.2199bbcb.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=kernel1@cyberdogtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox