From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Donald Hunter <donald.hunter@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jiri Pirko <jiri@resnulli.us>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/3] netlink: specs: team: avoid mangling multilines doc
Date: Sat, 13 Sep 2025 14:54:21 +0200 [thread overview]
Message-ID: <50d79030-9e45-4890-9fee-c0027caf07c9@kernel.org> (raw)
In-Reply-To: <20250912123518.7c51313b@kernel.org>
Hi Jakub,
Thank you for the reply!
On 12/09/2025 21:35, Jakub Kicinski wrote:
> On Fri, 12 Sep 2025 15:23:00 +0200 Matthieu Baerts (NGI0) wrote:
>> By default, strings defined in YAML at the next line are folded:
>> newlines are replaced by spaces. Here, the newlines are there for a
>> reason, and should be kept in the output.
>>
>> This can be fixed by adding the '|' symbol to use the "literal" style.
>> This issue was introduced by commit 387724cbf415 ("Documentation:
>> netlink: add a YAML spec for team"), but visible in the doc only since
>> the parent commit.
>>
>> Suggested-by: Donald Hunter <donald.hunter@gmail.com>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> ---
>> Documentation/netlink/specs/team.yaml | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/netlink/specs/team.yaml b/Documentation/netlink/specs/team.yaml
>> index cf02d47d12a458aaa7d45875a0a54af0093d80a8..fae40835386c82e934f205219cc5796e284999f1 100644
>> --- a/Documentation/netlink/specs/team.yaml
>> +++ b/Documentation/netlink/specs/team.yaml
>> @@ -25,7 +25,7 @@ definitions:
>> attribute-sets:
>> -
>> name: team
>> - doc:
>> + doc: |
>> The team nested layout of get/set msg looks like
>> [TEAM_ATTR_LIST_OPTION]
>> [TEAM_ATTR_ITEM_OPTION]
>>
>
> htmldoc is not super happy :(
>
> Documentation/netlink/specs/team.yaml:21: WARNING: Definition list ends without a blank line; unexpected unindent.
> Documentation/netlink/specs/team.yaml:21: WARNING: Definition list ends without a blank line; unexpected unindent.
Arf, I looked at the HTML version, I forgot to look for new warnings...
> Shooting from the hip -- maybe throwing :: at the end of the first line
> will make ReST treat the attrs as a block?
Indeed, I guess it is better to declare a code block instead of a list.
I will fix that in the next version.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-09-13 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 13:22 [PATCH net-next v2 0/3] tools: ynl: rst: display attribute-set doc Matthieu Baerts (NGI0)
2025-09-12 13:22 ` [PATCH net-next v2 1/3] " Matthieu Baerts (NGI0)
2025-09-12 13:23 ` [PATCH net-next v2 2/3] netlink: specs: team: avoid mangling multilines doc Matthieu Baerts (NGI0)
2025-09-12 19:35 ` Jakub Kicinski
2025-09-13 12:54 ` Matthieu Baerts [this message]
2025-09-12 13:23 ` [PATCH net-next v2 3/3] netlink: specs: explicitly declare block scalar strings Matthieu Baerts (NGI0)
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=50d79030-9e45-4890-9fee-c0027caf07c9@kernel.org \
--to=matttbe@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox