linux-kernel - Re: [PATCH 1/4] docs/memory-barriers.txt: Add a missed closing parenthesis

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: <20221009111000.GQ4196@paulmck-ThinkPad-P17-Gen-1>
Date:   Sun, 9 Oct 2022 04:10:00 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     SeongJae Park <sj@...nel.org>
Cc:     corbet@....net, linux-doc@...r.kernel.org,
        linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] docs/memory-barriers.txt: Add a missed closing
 parenthesis

On Sat, Oct 08, 2022 at 10:49:25AM -0700, SeongJae Park wrote:
> Description of io_stop_wc(), which added by commit d5624bb29f49
> ("asm-generic: introduce io_stop_wc() and add implementation for
> ARM64"), have unclosed parenthesis.  This commit closes it.
> 
> Fixes: d5624bb29f49 ("asm-generic: introduce io_stop_wc() and add implementation for ARM64")
> Signed-off-by: SeongJae Park <sj@...nel.org>

I have pulled this in, good eyes, and thank you!

On the other three, we have traditionally asked for an ack from a
Korean speaker.  Do we still feel the need to do this?

							Thanx, Paul

> ---
>  Documentation/memory-barriers.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
> index 06f80e3785c5..cc621decd943 100644
> --- a/Documentation/memory-barriers.txt
> +++ b/Documentation/memory-barriers.txt
> @@ -1966,7 +1966,7 @@ There are some more advanced barrier functions:
>   (*) io_stop_wc();
>  
>       For memory accesses with write-combining attributes (e.g. those returned
> -     by ioremap_wc(), the CPU may wait for prior accesses to be merged with
> +     by ioremap_wc()), the CPU may wait for prior accesses to be merged with
>       subsequent ones. io_stop_wc() can be used to prevent the merging of
>       write-combining memory accesses before this macro with those after it when
>       such wait has performance implications.
> -- 
> 2.17.1
>