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]
Message-ID: <20221129184559.GC4001@paulmck-ThinkPad-P17-Gen-1>
Date:   Tue, 29 Nov 2022 10:45:59 -0800
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Kushagra Verma <kushagra765@...look.com>
Cc:     Will Deacon <will@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Boqun Feng <boqun.feng@...il.com>,
        Mark Rutland <mark.rutland@....com>,
        Alan Stern <stern@...land.harvard.edu>,
        Andrea Parri <parri.andrea@...il.com>,
        Nicholas Piggin <npiggin@...il.com>,
        David Howells <dhowells@...hat.com>,
        Jade Alglave <j.alglave@....ac.uk>,
        Luc Maranget <luc.maranget@...ia.fr>,
        Akira Yokosawa <akiyks@...il.com>,
        Daniel Lustig <dlustig@...dia.com>,
        Joel Fernandes <joel@...lfernandes.org>,
        Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
        linux-arch@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation: Fixed a typo in atomic_t.txt

On Tue, Nov 29, 2022 at 06:50:59PM +0530, Kushagra Verma wrote:
> Fixed a typo in the word 'architecture'.
> 
> Signed-off-by: Kushagra Verma <kushagra765@...look.com>

Good eyes!  Queued for further review, thank you!

							Thanx, Paul

> ---
>  Documentation/atomic_t.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/atomic_t.txt b/Documentation/atomic_t.txt
> index 0f1ffa03db09..d7adc6d543db 100644
> --- a/Documentation/atomic_t.txt
> +++ b/Documentation/atomic_t.txt
> @@ -324,7 +324,7 @@ atomic operations.
>  
>  Specifically 'simple' cmpxchg() loops are expected to not starve one another
>  indefinitely. However, this is not evident on LL/SC architectures, because
> -while an LL/SC architecure 'can/should/must' provide forward progress
> +while an LL/SC architecture 'can/should/must' provide forward progress
>  guarantees between competing LL/SC sections, such a guarantee does not
>  transfer to cmpxchg() implemented using LL/SC. Consider:
>  
> -- 
> 2.38.1
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ