linux-kernel - Re: [PATCH v3 12/16] docs: PCI: acpi-info.rst: replace some characters

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: <20210616085104.0477bd7b@coco.lan>
Date:   Wed, 16 Jun 2021 08:51:04 +0200
From:   Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH v3 12/16] docs: PCI: acpi-info.rst: replace some
 characters

Em Wed, 19 May 2021 16:47:31 -0500
Bjorn Helgaas <helgaas@...nel.org> escreveu:

> On Sun, May 16, 2021 at 12:18:29PM +0200, Mauro Carvalho Chehab wrote:
> > The conversion tools used during DocBook/LaTeX/html/Markdown->ReST
> > conversion and some cut-and-pasted text contain some characters that
> > aren't easily reachable on standard keyboards and/or could cause
> > troubles when parsed by the documentation build system.
> > 
> > Replace the occurences of the following characters:
> > 
> > 	- U+00a0 (' '): NO-BREAK SPACE
> > 	  as it can cause lines being truncated on PDF output
> > 
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>  
> 
> Apparently you missed
> https://lore.kernel.org/r/20210512212938.GA2516413@bjorn-Precision-5520
> where I pointed out a couple issues (3 spaces after period in first
> hunk, extra whitespace at end of "know about it." hunk) and added my
> ack.
> 
> The subject line would be more useful as:
> 
>   docs: PCI: Replace non-breaking spaces to avoid PDF issues
> 
> It's fine to defer those issues if you want, 

Yeah, I opted to separate the changes into parts. This one is focused
on problematic chars that could lead into output issues. 

Once those get merged, I'll submit a separate one with things like curly
commas and dashes, as a couple of maintainers seem to have different
opinions about that.

> but this is still:
> 
> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>

Thanks!

Regards,
Mauro