From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Moritz Fischer <mdf@kernel.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Wu Hao <hao.wu@intel.com>,
Matthew Gerlach <matthew.gerlach@linux.intel.com>,
linux-fpga@vger.kernel.org, Tom Rix <trix@redhat.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] fpga: dfl-pci: rectify ReST formatting
Date: Thu, 14 Jan 2021 18:05:30 +0100 [thread overview]
Message-ID: <YAB52nrYo2MTdlzA@kroah.com> (raw)
In-Reply-To: <YAB1G9e4lCaKq0sq@epycbox.lan>
On Thu, Jan 14, 2021 at 08:45:15AM -0800, Moritz Fischer wrote:
> Hi Greg,
>
> On Mon, Jan 11, 2021 at 07:14:22PM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Jan 11, 2021 at 05:34:57PM +0100, Lukas Bulwahn wrote:
> > > On Mon, Jan 11, 2021 at 4:52 PM Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > On Mon, Jan 11, 2021 at 12:21:13PM +0100, 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.
> > > > >
> > > > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > > >
> > >
> > > > You forgot a Reported-by: tag for the person who notified you of this :(
> > >
> > > Greg, would you believe that I run 'make htmldocs' on linux-next myself?
> >
> > Sure, just seemed to match up with when Stephen reported this a few
> > hours earlier...
> >
> > thanks,
> >
> > greg k-h
>
> Are you waiting for a resend on this? Just asking because we got three
> versions of this patch by now :)
>
> I haven't re-sent this since you were already on the thread.
I'll just take this one, for some reason I thought Lukas was going to
resend, my fault...
greg k-h
next prev parent reply other threads:[~2021-01-14 17:06 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
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 [this message]
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=YAB52nrYo2MTdlzA@kroah.com \
--to=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 \
--cc=trix@redhat.com \
/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).