netdev - Re: [PATCH net-next 01/10] net: bridge: add document for IFLA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 21 Nov 2023 11:28:30 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
	David Ahern <dsahern@...nel.org>,
	Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
	Ido Schimmel <idosch@...sch.org>,
	Nikolay Aleksandrov <razor@...ckwall.org>,
	Roopa Prabhu <roopa@...dia.com>,
	Stephen Hemminger <stephen@...workplumber.org>,
	Florian Westphal <fw@...len.de>, Andrew Lunn <andrew@...n.ch>,
	Florian Fainelli <f.fainelli@...il.com>,
	Vladimir Oltean <olteanv@...il.com>, Jiri Pirko <jiri@...nulli.us>,
	Marc Muehlfeld <mmuehlfe@...hat.com>
Subject: Re: [PATCH net-next 01/10] net: bridge: add document for IFLA_BR enum

On Sat, Nov 18, 2023 at 09:45:25AM -0800, Jakub Kicinski wrote:
> On Fri, 17 Nov 2023 17:31:36 +0800 Hangbin Liu wrote:
> > Add document for IFLA_BR enum so we can use it in
> > Documentation/networking/bridge.rst.
> 
> Did you consider writing a YAML spec instead?
> 
> It's unlikely to be usable today with YNL due to all the classic
> netlink vs genetlink differences, but Breno is working on rendering 
> the specs in documentation:
> 
> https://lore.kernel.org/all/20231113202936.242308-1-leitao@debian.org/
> 
> so in terms of just documenting attributes it may be good enough.
> It may possibly be nice to have that documentation folder as "one 
> stop shop" for all of netlink?

Thanks for this info. Will the YAML spec be build by the document team?
I'd prefer all the doc shows in https://www.kernel.org/doc/html/latest/
so users could find the doc easily.

It would be good if there is an example in Documentation/netlink/specs/ (when
the patch applied) so I can take as a reference :)

Thanks
Hangbin
> 
> Absolutely no strong preference on my side, just wanted to make
> sure you're aware of that work.