From: Tom Rix <trix@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Wu Hao <hao.wu@intel.com>, Moritz Fischer <mdf@kernel.org>,
Matthew Gerlach <matthew.gerlach@linux.intel.com>,
linux-fpga@vger.kernel.org, linux-doc@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] fpga: dfl-pci: rectify ReST formatting
Date: Mon, 11 Jan 2021 08:07:35 -0800 [thread overview]
Message-ID: <422569e9-b85c-7724-51ea-bcbdf6c26bf6@redhat.com> (raw)
In-Reply-To: <X/x0cJ2N0/VA81FK@kroah.com>
On 1/11/21 7:53 AM, Greg Kroah-Hartman wrote:
> On Mon, Jan 11, 2021 at 07:11:59AM -0800, Tom Rix wrote:
>> On 1/11/21 3:21 AM, Lukas Bulwahn wrote:
>>> Commit fa41d10589be ("fpga: dfl-pci: locate DFLs by PCIe vendor specific
>>> capability") provides documentation to the FPGA Device Feature List (DFL)
>>> Framework Overview, but introduced new documentation warnings:
>>>
>>> ./Documentation/fpga/dfl.rst:
>>> 505: WARNING: Title underline too short.
>>> 523: WARNING: Unexpected indentation.
>>> 523: WARNING: Blank line required after table.
>>> 524: WARNING: Block quote ends without a blank line; unexpected unindent.
>>>
>>> Rectify ReST formatting in ./Documentation/fpga/dfl.rst.
>> Can you explain how to reproduce this problem ?
> 'make htmldocs'
Thanks, I have verified the problem and its resolution.
Tested-by: Tom Rix <trix@redhat.com>
>
next prev parent reply other threads:[~2021-01-11 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 11:21 [PATCH -next] fpga: dfl-pci: rectify ReST formatting Lukas Bulwahn
2021-01-11 15:11 ` Tom Rix
2021-01-11 15:53 ` Greg Kroah-Hartman
2021-01-11 16:07 ` Tom Rix [this message]
2021-01-11 15:53 ` Greg Kroah-Hartman
2021-01-11 16:34 ` Lukas Bulwahn
2021-01-11 18:14 ` Greg Kroah-Hartman
2021-01-14 16:45 ` Moritz Fischer
2021-01-14 17:05 ` Greg Kroah-Hartman
2021-01-11 15:55 ` Moritz Fischer
2021-01-11 17:10 ` Lukas Bulwahn
2021-01-11 18:16 ` matthew.gerlach
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=422569e9-b85c-7724-51ea-bcbdf6c26bf6@redhat.com \
--to=trix@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=matthew.gerlach@linux.intel.com \
--cc=mdf@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;
as well as URLs for NNTP newsgroup(s).