linux-kernel - Re: [PATCH 0/4] docs: e100[0] fix build errors

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: <ba768d6c-dd21-3600-5cba-151b5d6185f1@infradead.org>
Date:   Fri, 22 Jun 2018 13:22:37 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     "Tobin C. Harding" <me@...in.cc>, Jonathan Corbet <corbet@....net>
Cc:     Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
        "David S. Miller" <davem@...emloft.net>, linux-doc@...r.kernel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] docs: e100[0] fix build errors

Hi Tobin,

On 06/21/2018 05:37 PM, Tobin C. Harding wrote:
> Hi Jonathan,
> 
> This patch set fixes current docs build failure on Linus' mainline
> 
> commit: (ba4dbdedd3ed Merge tag 'jfs-4.18' of git://github.com/kleikamp/linux-shaggy)
> 
> (FYI this is 8 commits after Linux 4.18-rc1).
> 
> And also same build errors on today's linux-next
> 
> 8439c34f07a3 (tag: next-20180621, linux-next/master, linux-next) Add linux-next specific files for 20180621
> 
> 
> I split the patches in between the two drivers to enable use of the
> 'Fixes:' tag.
> 
> Tobin C. Harding (4):
>   Documentation: e100: Use correct heading adornment
>   Documentation: e1000: Use correct heading adornment
>   Documentation: e100: Fix docs build error
>   Documentation: e1000: Fix docs build error
> 
>  Documentation/networking/e100.rst  | 112 +++++++++++++++--------------
>  Documentation/networking/e1000.rst |  76 ++++++++++----------
>  2 files changed, 96 insertions(+), 92 deletions(-)

I am still seeing a few warnings (your 4 patches applied to
linux-next-20180622):

linux-next-20180622/Documentation/networking/e100.rst:57: WARNING: Literal block expected; none found.
linux-next-20180622/Documentation/networking/e100.rst:68: WARNING: Literal block expected; none found.
linux-next-20180622/Documentation/networking/e100.rst:75: WARNING: Literal block expected; none found.
linux-next-20180622/Documentation/networking/e100.rst:84: WARNING: Literal block expected; none found.
linux-next-20180622/Documentation/networking/e100.rst:93: WARNING: Inline emphasis start-string without end-string.
linux-next-20180622/Documentation/networking/e1000.rst:83: ERROR: Unexpected indentation.
linux-next-20180622/Documentation/networking/e1000.rst:84: WARNING: Block quote ends without a blank line; unexpected unindent.
linux-next-20180622/Documentation/networking/e1000.rst:173: WARNING: Definition list ends without a blank line; unexpected unindent.
linux-next-20180622/Documentation/networking/e1000.rst:236: WARNING: Definition list ends without a blank line; unexpected unindent.

You didn't get these warnings?  or they weren't important?
or "perfect" was not your primary goal?   :)   [which is fine]

[I see around 50 similar doc formatting warnings/errors in the entire
Documentation build.]

Anyway, much better than it was.  Thanks.

Tested-by: Randy Dunlap <rdunlap@...radead.org>

-- 
~Randy