All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: David Gow <davidgow@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	KUnit Development <kunit-dev@googlegroups.com>,
	Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Harinder Singh <sharinder@google.com>,
	Tim Bird <tim.bird@sony.com>
Subject: Re: [PATCH] Documentation: kunit: eliminate code-block warnings
Date: Fri, 1 Apr 2022 23:24:58 -0700	[thread overview]
Message-ID: <87010ada-86a2-4fb4-7ffd-8db1b656598d@infradead.org> (raw)
In-Reply-To: <CABVgOSk-8O9jLZncbJvsZdTaA9VjBKbByktnwhPCNJHWME2Nug@mail.gmail.com>

Hi David,

On 3/31/22 23:26, David Gow wrote:
> On Fri, Apr 1, 2022 at 10:47 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> Fix Sphinx complaints about code-block directive missing an argument.
>> For start.rst, add "none" since that is already heavily used in that
>> file. For run_wrapper.rst, use the simpler "::" literal block instead.
>>
>> dev-tools/kunit/start.rst:83: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>>
>> dev-tools/kunit/run_wrapper.rst:17: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:23: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:31: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:51: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:57: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:78: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:85: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:109: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:116: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:124: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:139: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>> dev-tools/kunit/run_wrapper.rst:162: WARNING: Error in "code-block" directive:
>> 1 argument(s) required, 0 supplied.
>>
>> Fixes: c48b9ef1f794 ("Documentation: KUnit: Rewrite getting started")
>> Fixes: 46201d47d6c4 ("Documentation: kunit: Reorganize documentation related to running tests")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Brendan Higgins <brendanhiggins@google.com>
>> Cc: linux-kselftest@vger.kernel.org
>> Cc: kunit-dev@googlegroups.com
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: linux-doc@vger.kernel.org
>> Cc: Harinder Singh <sharinder@google.com>
>> Cc: Tim Bird <tim.bird@sony.com>
>> ---
> 
> Thanks for fixing these.
> 
> Out of curiosity, is there a particular config option or version you
> need to set in sphinx to get these warnings? My setup (with Sphinx
> 4.3.2) doesn't warn on this.

No options. I expect that it's just an older version of Sphinx that
is causing this. I have v1.8.5 installed (comes with OpenSUSE Leap 15.3).

> Nevertheless, I'll keep a closer eye on code-block directives in future.
> 
> Reviewed-by: David Gow <davidgow@google.com>

thanks.
-- 
~Randy

  reply	other threads:[~2022-04-02  6:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  2:47 [PATCH] Documentation: kunit: eliminate code-block warnings Randy Dunlap
2022-04-01  6:26 ` David Gow
2022-04-02  6:24   ` Randy Dunlap [this message]
2022-06-19 23:56 ` Randy Dunlap
2022-06-24 19:27 ` Jonathan Corbet
2022-06-25 15:12   ` Randy Dunlap
2022-06-28  7:17     ` Mauro Carvalho Chehab
2022-06-28 14:20       ` Randy Dunlap

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=87010ada-86a2-4fb4-7ffd-8db1b656598d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=brendanhiggins@google.com \
    --cc=corbet@lwn.net \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sharinder@google.com \
    --cc=tim.bird@sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.