public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/7] More kernel-doc unit tests
Date: Wed, 25 Mar 2026 13:40:18 -0600	[thread overview]
Message-ID: <871ph7g0kd.fsf@trenco.lwn.net> (raw)
In-Reply-To: <874im3g0w6.fsf@trenco.lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
>> Hi Jon,
>>
>> This series comes after
>>         https://lore.kernel.org/linux-doc/20260318104321.53065c27@foz.lan/T/#t
>>
>> and contains the remaining patches I have ready to be merged.
>>
>> Its focus is primarly on adding unit tests for some corner
>> cases. Several of such tests came from Randy, and were already
>> previously submitted on some old series.
>>
>> I added a couple of extra tests there to check if tables and code
>> blocks will be properly producing rst and man content.
>>
>> Due to such test, I ended discovering one bug, fixed on the last
>> patch on this series.
>>
>> On this series, the actual tests are not part of the unit test
>> source code. Instead, they're loaded from an yaml file that
>> uses a properly defined schema. One of the tests check if the
>> file follows such schema.
>
> I've applied these, thanks.

Actually nevermind...it appears that this series was superseded by the
set sent on Monday?  I've applied the newer set instead.

Thanks,

jon

      reply	other threads:[~2026-03-25 19:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 14:26 [PATCH 0/7] More kernel-doc unit tests Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 1/7] docs: kdoc_parser: add some debug for variable parsing Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 2/7] unittests: test_kdoc_parser: add command line arg to read a YAML file Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 3/7] MAINTAINERS: update documentation scripts to add unittests Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 4/7] docs: tools: include kdoc_yaml_file at documentation Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 5/7] docs: kdoc_yaml_file: add a representer to make strings look nicer Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 6/7] docs: kdoc-test.yaml: add more tests Mauro Carvalho Chehab
2026-03-18 14:26 ` [PATCH 7/7] docs: kdoc_output: fix handling of simple tables Mauro Carvalho Chehab
2026-03-25 19:33 ` [PATCH 0/7] More kernel-doc unit tests Jonathan Corbet
2026-03-25 19:40   ` Jonathan Corbet [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=871ph7g0kd.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=aleksandr.loktionov@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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