linux-kernel - Re: [PATCH] docs/sp_SP: Remove ZERO WIDTH SPACE in memory-barriers.txt

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: <41839138-3d85-ea82-7832-5da5f9addeb1@amd.com>
Date:   Wed, 29 Mar 2023 08:06:10 -0500
From:   Carlos Bilbao <carlos.bilbao@....com>
To:     Akira Yokosawa <akiyks@...il.com>, Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs/sp_SP: Remove ZERO WIDTH SPACE in
 memory-barriers.txt

On 3/29/23 12:22 AM, Akira Yokosawa wrote:
> As this file is included literally, ZERO WIDTH SPACE causes
> "make pdfdocs" to emit messages which read:
> 
>   Missing character: There is no  (U+200B) in font DejaVu Sans Mono/OT:script=latn;language=dflt;!
>   Missing character: There is no  (U+200B) in font DejaVu Sans Mono/OT:script=latn;language=dflt;!
> 
> U+200B (ZERO WIDTH SPADE) has no effect in literal blocks.
> Remove them and get rid of those noises.
> 
> Signed-off-by: Akira Yokosawa <akiyks@...il.com>
> Cc: Carlos Bilbao <carlos.bilbao@....com>
> Cc: Jonathan Corbet <corbet@....net>
> ---
> Hi,
> 
> Offending commit is 259b007f5729 ("docs/sp_SP: Add memory-barriers.txt
> Spanish translation") merged into v6.2.
> As this is not a bug fix, I'm not putting a Fixes: tag.
> 
> Note: It might be hard for human eyes to see where the removed
> ZERO WIDTH SPACEs were. :-)
> 
>         Thanks, Akira

Good catch, Akira! Acked-by: Carlos Bilbao <carlos.bilbao@....com>

> --
>  Documentation/translations/sp_SP/memory-barriers.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/translations/sp_SP/memory-barriers.txt b/Documentation/translations/sp_SP/memory-barriers.txt
> index f62bd797216d..27097a808c88 100644
> --- a/Documentation/translations/sp_SP/memory-barriers.txt
> +++ b/Documentation/translations/sp_SP/memory-barriers.txt
> @@ -604,7 +604,7 @@ READ_ONCE() para DEC Alpha, lo que significa que las únicas personas que
>  necesitan prestar atención a esta sección son aquellas que trabajan en el
>  código específico de la arquitectura DEC Alpha y aquellas que trabajan en
>  READ_ONCE() por dentro. Para aquellos que lo necesitan, y para aquellos que
> -estén interesados desde un punto de vista histórico, aquí está la historia
> +estén interesados desde un punto de vista histórico, aquí está la historia
>  de las barreras de dependencia de dirección.
>  
>  [!] Si bien las dependencias de direcciones se observan tanto en carga a
> 
> base-commit: 4f1bb0386dfc0bda78ddad0e4fb3cd519b2886ab

Thanks,
Carlos