From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>,
Roopa Prabhu <roopa@nvidia.com>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ido Schimmel <idosch@idosch.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [RFC Draft PATCH net-next 0/1] Bridge doc update
Date: Wed, 20 Sep 2023 17:19:48 +0800 [thread overview]
Message-ID: <ZQq5NDqPAbwi98yU@Laptop-X1> (raw)
In-Reply-To: <20230913092854.1027336-1-liuhangbin@gmail.com>
Hi Nikolay, Roopa,
Do you have any comments for this RFC?
Thanks
Hangbin
On Wed, Sep 13, 2023 at 05:28:52PM +0800, Hangbin Liu wrote:
> Hi,
>
> After a long busy period. I got time to check how to update the bridge doc.
> Here is the previous discussion we made[1].
>
> In this update. I plan to convert all the bridge description/comments to
> the kernel headers. And add sphinx identifiers in the doc to show them
> directly. At the same time, I wrote a script to convert the description
> in kernel header file to iproute2 man doc. With this, there is no need
> to maintain the doc in 2 places.
>
> For the script. I use python docutils to read the rst comments. When dump
> the man page. I do it manually to match the current ip link man page style.
> I tried rst2man, but the generated man doc will break the current style.
> If you have any other better way, please tell me.
>
> [1] https://lore.kernel.org/netdev/5ddac447-c268-e559-a8dc-08ae3d124352@blackwall.org/
>
>
> Hangbin Liu (1):
> Doc: update bridge doc
>
> Documentation/networking/bridge.rst | 85 ++++++++++--
> include/uapi/linux/if_bridge.h | 24 ++++
> include/uapi/linux/if_link.h | 194 ++++++++++++++++++++++++++++
> 3 files changed, 293 insertions(+), 10 deletions(-)
>
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-09-20 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 9:28 [RFC Draft PATCH net-next 0/1] Bridge doc update Hangbin Liu
2023-09-13 9:28 ` [RFC Draft PATCH net-next] Doc: update bridge doc Hangbin Liu
2023-09-13 9:28 ` [RFC Draft PATCH iproute2-next] tools: add a tool to generate bridge man doc Hangbin Liu
2023-09-13 11:22 ` [RFC Draft PATCH net-next 0/1] Bridge doc update Stephen Hemminger
2023-09-14 3:06 ` Hangbin Liu
2023-09-13 11:25 ` Stephen Hemminger
2023-09-20 9:19 ` Hangbin Liu [this message]
2023-09-20 10:38 ` Nikolay Aleksandrov
2023-09-20 14:17 ` Hangbin Liu
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=ZQq5NDqPAbwi98yU@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=stephen@networkplumber.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