From: Simon Arlott <simon@fire.lp0.eu>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mips@linux-mips.org, trivial@kernel.org
Subject: Re: [PATCH] spelling fixes: arch/mips/
Date: Fri, 11 May 2007 20:56:16 +0100 [thread overview]
Message-ID: <4644CA60.8080809@simon.arlott.org.uk> (raw)
In-Reply-To: <4644C721.501@simon.arlott.org.uk>
On 11/05/07 20:42, Simon Arlott wrote:
> diff --git a/arch/mips/kernel/semaphore.c b/arch/mips/kernel/semaphore.c
> index 1265358..b363604 100644
> --- a/arch/mips/kernel/semaphore.c
> +++ b/arch/mips/kernel/semaphore.c
> @@ -33,7 +33,7 @@
> * return old_count;
> *
> * On machines without lld/scd we need a spinlock to make the
> manipulation of
> - * sem->count and sem->waking atomic. Scalability isn't an issue because
> + * sem->count and sem->waking atomic. Scalibility isn't an issue because
> * this lock is used on UP only so it's just an empty variable.
> */
> static inline int __sem_update_count(struct semaphore *sem, int incr)
I thought I'd reverted that mistake... it was correct already, too many
"capability" fixes confusing me :/
--
Simon Arlott
prev parent reply other threads:[~2007-05-11 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 19:42 [PATCH] spelling fixes: arch/mips/ Simon Arlott
2007-05-11 19:56 ` Simon Arlott [this message]
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=4644CA60.8080809@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=trivial@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.