linux-kernel - Re: [PATCH] ia64: kernel: Few typos fixed in the file fsys.S

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e26a1461-0d05-d79c-7688-de45d285e068@infradead.org>
Date:   Wed, 10 Mar 2021 22:15:30 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>,
        linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ia64: kernel: Few typos fixed in the file fsys.S

On 3/10/21 10:10 PM, Bhaskar Chowdhury wrote:
> 
> Mundane spelling fixes.
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.org>

but no maintainer Cc:ed to pick it up...

> ---
>  arch/ia64/kernel/fsys.S | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/ia64/kernel/fsys.S b/arch/ia64/kernel/fsys.S
> index 0750a716adc7..2094f3249019 100644
> --- a/arch/ia64/kernel/fsys.S
> +++ b/arch/ia64/kernel/fsys.S
> @@ -172,7 +172,7 @@ ENTRY(fsys_gettimeofday)
>  	// r25 = itc_lastcycle value
>  	// r26 = address clocksource cycle_last
>  	// r27 = (not used)
> -	// r28 = sequence number at the beginning of critcal section
> +	// r28 = sequence number at the beginning of critical section
>  	// r29 = address of itc_jitter
>  	// r30 = time processing flags / memory address
>  	// r31 = pointer to result
> @@ -432,7 +432,7 @@ GLOBAL_ENTRY(fsys_bubble_down)
>  	 *	- r29: psr
>  	 *
>  	 * We used to clear some PSR bits here but that requires slow
> -	 * serialization.  Fortuntely, that isn't really necessary.
> +	 * serialization.  Fortunately, that isn't really necessary.
>  	 * The rationale is as follows: we used to clear bits
>  	 * ~PSR_PRESERVED_BITS in PSR.L.  Since
>  	 * PSR_PRESERVED_BITS==PSR.{UP,MFL,MFH,PK,DT,PP,SP,RT,IC}, we
> --


-- 
~Randy