From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 0/3] Some kernel-doc fixes
Date: Wed, 04 Feb 2026 13:06:24 +0200 [thread overview]
Message-ID: <97e595a4082cc79ecec698cda1fb3dbaf6e94c70@intel.com> (raw)
In-Reply-To: <20260203160536.41c30f47@foz.lan>
On Tue, 03 Feb 2026, Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> ... pyyaml output is not user-friendly. Maybe there are ways
> to make it use a more compact/nicer notation, but digging
> into its documentation is not easy:
>
> https://pyyaml.org/wiki/PyYAMLDocumentation
>
> and it is not complete.
Side note, I really like using StrictYAML [1] with a schema for parsing
YAML. It's maybe slower, and probably won't help with the output either,
but the YAML type safety and validation are such nice features. (See the
Norway Problem.)
BR,
Jani.
[1] https://hitchdev.com/strictyaml/
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-02-04 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:03 [PATCH 0/3] Some kernel-doc fixes Mauro Carvalho Chehab
2026-01-27 8:03 ` [PATCH 1/3] docs: kdoc: Fix pdfdocs build for tools Mauro Carvalho Chehab
2026-01-27 8:03 ` [PATCH 2/3] docs: sphinx-build-wrapper: allow -v override -q Mauro Carvalho Chehab
2026-01-27 8:03 ` [PATCH 3/3] tools: sphinx-build-wrapper: improve its help message Mauro Carvalho Chehab
2026-01-27 17:34 ` [PATCH 0/3] Some kernel-doc fixes Jonathan Corbet
2026-02-02 17:01 ` Jonathan Corbet
2026-02-02 18:15 ` Mauro Carvalho Chehab
2026-02-03 10:52 ` Jani Nikula
2026-02-03 15:05 ` Mauro Carvalho Chehab
2026-02-04 11:06 ` Jani Nikula [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=97e595a4082cc79ecec698cda1fb3dbaf6e94c70@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+huawei@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