[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a1d0d61c-d6e9-aee6-fe67-e35f42b76a04@gmail.com>
Date: Mon, 27 Mar 2023 23:39:54 +0900
From: Akira Yokosawa <akiyks@...il.com>
To: bagasdotme@...il.com
Cc: corbet@....net, davem@...emloft.net, donald.hunter@...il.com,
donald.hunter@...hat.com, edumazet@...gle.com, kuba@...nel.org,
linux-doc@...r.kernel.org, netdev@...r.kernel.org,
pabeni@...hat.com
Subject: Re: [PATCH net-next v5 6/7] docs: netlink: document struct support
for genetlink-legacy
On Date: Mon, 27 Mar 2023 19:44:59 +0700, Bagas Sanjaya wrote:
> On Mon, Mar 27, 2023 at 09:31:37AM +0100, Donald Hunter wrote:
[...]
>> +
>> +Here is the struct definition from above, declared in YAML:
>> +
>> +.. code-block:: yaml
>> +
>> + definitions:
>> + -
>> + name: message-header
>> + type: struct
>> + members:
>> + -
>> + name: a
>> + type: u8
>> + -
>> + name: b
>> + type: u16
>> + -
>> + name: c
>> + type: u8
>> +
>
> Nit: The indentation for code-block codes should be relative to
> code-block:: declaration (e.g. if it starts from column 4, the first
> column of code is also at 4).
Hey Bagas,
I don't believe there is any such restriction. :-\
Where did you find it ?
Thanks, Akira
Powered by blists - more mailing lists