[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFd5g47+3TN4pOdeM0YmJpMP2uKnpJYUY_OXmqmZEn8OcVz6ow@mail.gmail.com>
Date: Tue, 19 Nov 2019 17:14:20 -0800
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: shuah <shuah@...nel.org>, David Gow <davidgow@...gle.com>,
KUnit Development <kunit-dev@...glegroups.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
"Theodore Ts'o" <tytso@....edu>
Subject: Re: [PATCH linux-kselftest/test v3] Documentation: kunit: add
documentation for kunit_tool
On Tue, Nov 19, 2019 at 4:27 PM Randy Dunlap <rdunlap@...radead.org> wrote:
>
> On 11/18/19 4:31 PM, Brendan Higgins wrote:
> > +How do I use kunit_tool?
> > +=================================
>
> Hi,
> I haven't tested this, but Sphinx (or some doc tool) usually complains if the
> underline length is not the same as the header text length. (I.e., use fewer
> = signs above.)
Hmmm...Sphinx and checkpatch didn't complain. I wonder if it is a
different script, or maybe I have to use a particular option with
Sphinx.
In any case, thanks for catching this!
> > +
> > +If a kunitconfig is present at the root directory, all you have to do is:
> > +
> > +.. code-block:: bash
> > +
> > + ./tools/testing/kunit/kunit.py run
Powered by blists - more mailing lists