linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Logan Gunthorpe <logang@deltatee.com>,
	corbet@lwn.net, hch@lst.de, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	sfr@canb.auug.org.au
Subject: Re: linux-next: build warning after merge of the dma-mapping tree
Date: Thu, 28 Jul 2022 15:57:58 +0700	[thread overview]
Message-ID: <YuJPllC3SHqOR1ez@debian.me> (raw)
In-Reply-To: <8a3a24b5-1f2f-d2bd-f2c9-2bda9298e23c@gmail.com>

On Thu, Jul 28, 2022 at 11:23:34AM +0900, Akira Yokosawa wrote:
> > Oh, hmm, I thought I addressed this when I added the extra line at the
> > end of the comment, but it seems the htmldocs is a bit fussier than that
> > with the white space. 
> > 
> > The only way I can seem to suppress that error is by adding another tab
> > character in the list; see below.
> 
> I think all you need is to see the reference at:
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#option-lists
> 
> There are examples for long options.
> 

Hi Akira,

I read the reference, and for the long option case, I see:

> --very-long-option  A VMS-style option.  Note the adjustment for
>                     the required two spaces.
>
> --an-even-longer-option
>            The description can also start on the next line.

I interpreted that for the first case above, two spaces separator between
the first and second sentence of option description is required, right?

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2022-07-28  8:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 11:48 linux-next: build warning after merge of the dma-mapping tree Stephen Rothwell
2022-07-27 18:32 ` Logan Gunthorpe
2022-07-28  2:23   ` Akira Yokosawa
2022-07-28  8:57     ` Bagas Sanjaya [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-18 22:54 Stephen Rothwell
2021-08-19  7:02 ` Christoph Hellwig
2021-08-13  7:11 Stephen Rothwell
2021-09-03  6:45 ` Stephen Rothwell
2021-09-06 12:41   ` Christoph Hellwig
2020-09-02  0:03 Stephen Rothwell
2020-09-02 15:25 ` Christoph Hellwig
2018-10-01 22:35 Stephen Rothwell
2018-10-02 14:22 ` Christoph Hellwig
2017-09-03 22:34 Stephen Rothwell
2017-09-04  5:51 ` Christoph Hellwig

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=YuJPllC3SHqOR1ez@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=hch@lst.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sfr@canb.auug.org.au \
    /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).