mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao@amd.com>, Akira Yokosawa <akiyks@gmail.com>
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 10:47:19 -0600	[thread overview]
Message-ID: <87a5zvjyi0.fsf@meer.lwn.net> (raw)
In-Reply-To: <41839138-3d85-ea82-7832-5da5f9addeb1@amd.com>

Carlos Bilbao <carlos.bilbao@amd.com> writes:

> 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>

Carlos, when you put an Acked-by in the middle of a line like that, b4
no longer sees it.

Anyway, I've applied the patch, thanks.

jon

      reply	other threads:[~2023-03-29 16:47 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
2023-03-29 16:47   ` Jonathan Corbet [this message]

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=87a5zvjyi0.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=carlos.bilbao@amd.com \
    --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®