linux-kernel - Re: [PATCH 1/1] Staging: Fixed spelling mistake

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 18 Dec 2009 15:33:38 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Shaun Patterson <shaunpatterson@...il.com>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] Staging: Fixed spelling mistake

On Sat, 5 Dec 2009, Shaun Patterson wrote:

> 
> Signed-off-by: Shaun Patterson <shaunpatterson@...il.com>
> ---
>  arch/x86/kernel/vmiclock_32.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/kernel/vmiclock_32.c b/arch/x86/kernel/vmiclock_32.c
> index 611b9e2..a58ccae 100644
> --- a/arch/x86/kernel/vmiclock_32.c
> +++ b/arch/x86/kernel/vmiclock_32.c
> @@ -171,7 +171,7 @@ static int vmi_timer_next_event(unsigned long delta,
>  {
>  	/* Unfortunately, set_next_event interface only passes relative
>  	 * expiry, but we want absolute expiry.  It'd be better if were
> -	 * were passed an aboslute expiry, since a bunch of time may
> +	 * were passed an absolute expiry, since a bunch of time may
>  	 * have been stolen between the time the delta is computed and
>  	 * when we set the alarm below. */
>  	cycle_t now = vmi_timer_ops.get_cycle_counter(vmi_counter(VMI_ONESHOT));

As this seems to be present in current Linus' tree still, I have applied 
it to trivial queue (after fixing the subject, nothing to do with 
staging).

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