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-ia64@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] spelling fixes: arch/ia64/
Date: Fri, 11 May 2007 19:55:12 +0000 [thread overview]
Message-ID: <4644CA20.2060606@simon.arlott.org.uk> (raw)
In-Reply-To: <4644C6FD.6010004@simon.arlott.org.uk>
On 11/05/07 20:41, Simon Arlott wrote:
> diff --git a/arch/ia64/kernel/time.c b/arch/ia64/kernel/time.c
> index a06667c..bf7e7b5 100644
> --- a/arch/ia64/kernel/time.c
> +++ b/arch/ia64/kernel/time.c
> @@ -216,7 +216,7 @@ ia64_init_itm (void)
> #ifdef CONFIG_SMP
> /* On IA64 in an SMP configuration ITCs are never accurately
> synchronized.
> * Jitter compensation requires a cmpxchg which may limit
> - * the scalability of the syscalls for retrieving time.
> + * the scalibility of the syscalls for retrieving time.
> * The ITC synchronization is usually successful to within a few
> * ITC ticks but this is not a sure thing. If you need to improve
> * timer performance in SMP situations then boot the kernel with
> the
I thought I'd reverted that mistake... it was correct already :/
--
Simon Arlott
WARNING: multiple messages have this Message-ID (diff)
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-ia64@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] spelling fixes: arch/ia64/
Date: Fri, 11 May 2007 20:55:12 +0100 [thread overview]
Message-ID: <4644CA20.2060606@simon.arlott.org.uk> (raw)
In-Reply-To: <4644C6FD.6010004@simon.arlott.org.uk>
On 11/05/07 20:41, Simon Arlott wrote:
> diff --git a/arch/ia64/kernel/time.c b/arch/ia64/kernel/time.c
> index a06667c..bf7e7b5 100644
> --- a/arch/ia64/kernel/time.c
> +++ b/arch/ia64/kernel/time.c
> @@ -216,7 +216,7 @@ ia64_init_itm (void)
> #ifdef CONFIG_SMP
> /* On IA64 in an SMP configuration ITCs are never accurately
> synchronized.
> * Jitter compensation requires a cmpxchg which may limit
> - * the scalability of the syscalls for retrieving time.
> + * the scalibility of the syscalls for retrieving time.
> * The ITC synchronization is usually successful to within a few
> * ITC ticks but this is not a sure thing. If you need to improve
> * timer performance in SMP situations then boot the kernel with
> the
I thought I'd reverted that mistake... it was correct already :/
--
Simon Arlott
next prev parent reply other threads:[~2007-05-11 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 19:41 [PATCH] spelling fixes: arch/ia64/ Simon Arlott
2007-05-11 19:41 ` Simon Arlott
2007-05-11 19:55 ` Simon Arlott [this message]
2007-05-11 19:55 ` Simon Arlott
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=4644CA20.2060606@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.