From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Akira Yokosawa <akiyks@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/sp_SP: Remove ZERO WIDTH SPACE in memory-barriers.txt
Date: Wed, 29 Mar 2023 08:06:10 -0500 [thread overview]
Message-ID: <41839138-3d85-ea82-7832-5da5f9addeb1@amd.com> (raw)
In-Reply-To: <c38176c7-c30a-4c2c-3516-8d3be1c267dc@gmail.com>
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@gmail.com>
> Cc: Carlos Bilbao <carlos.bilbao@amd.com>
> Cc: Jonathan Corbet <corbet@lwn.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@amd.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
next prev parent reply other threads:[~2023-03-29 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 5:22 Akira Yokosawa
2023-03-29 13:06 ` Carlos Bilbao [this message]
2023-03-29 16:47 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41839138-3d85-ea82-7832-5da5f9addeb1@amd.com \
--to=carlos.bilbao@amd.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®