From: shuah <shuah@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>, Lothar Rubusch <l.rubusch@gmail.com>
Cc: brendanhiggins@google.com, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, shuah <shuah@kernel.org>
Subject: Re: [PATCH v5] Documentation: test.h - fix warnings
Date: Fri, 22 May 2020 16:24:48 -0600 [thread overview]
Message-ID: <7dcdabd2-3a7c-4004-6355-12e44b4b0456@kernel.org> (raw)
In-Reply-To: <20200421133313.5f41fcf4@lwn.net>
On 4/21/20 1:33 PM, Jonathan Corbet wrote:
> On Wed, 15 Apr 2020 20:16:53 +0000
> Lothar Rubusch <l.rubusch@gmail.com> wrote:
>
>> Fix warnings at 'make htmldocs', and formatting issues in the resulting
>> documentation.
>>
>> - test.h: Fix annotation in kernel-doc parameter description.
>>
>> - Documentation/*.rst: Fixing formatting issues, and a duplicate label
>> issue due to usage of sphinx.ext.autosectionlabel and identical labels
>> within one document (sphinx warning)
>>
>> Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
>> ---
>> v2: Several documentation fixes
>>
>> v3: Do not touch API documentation index
>>
>> v4: Replace macro argument in test.h by named variadic argument
>>
>> v5: Patch format fixed
>>
>> NB: checkpatch.pl will complain about flow control statements (i.e. usage
>> of "return") within the macro kunit_test_suites(suites_list...).
>>
>> Better? I feel I'm making you a lot of extra work. I'm really sorry for
>> all this fuzz!
>
> So I'm assuming this will go via Shuah's tree; let me know if that's
> incorrect.
>
Applied to linux-kselftest kunit for Linux 5.8-rc1.
thanks,
-- Shuah
prev parent reply other threads:[~2020-05-22 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 20:16 [PATCH v5] Documentation: test.h - fix warnings Lothar Rubusch
2020-04-20 16:49 ` Brendan Higgins
2020-04-21 19:33 ` Jonathan Corbet
2020-05-22 22:24 ` shuah [this message]
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=7dcdabd2-3a7c-4004-6355-12e44b4b0456@kernel.org \
--to=shuah@kernel.org \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=kunit-dev@googlegroups.com \
--cc=l.rubusch@gmail.com \
--cc=linux-kselftest@vger.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