linux-kernel - Re: [PATCH 4/4] docs: netlink: store generated .rst files at Documentation/output

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]

Message-ID: <20250610140724.5f183759@kernel.org>
Date: Tue, 10 Jun 2025 14:07:24 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Breno Leitao <leitao@...ian.org>, Linux Doc Mailing List
 <linux-doc@...r.kernel.org>, Jonathan Corbet <corbet@....net>, Akira
 Yokosawa <akiyks@...il.com>, "David S. Miller" <davem@...emloft.net>,
 Ignacio Encinas Rubio <ignacio@...cinas.com>, Marco Elver
 <elver@...gle.com>, Shuah Khan <skhan@...uxfoundation.org>, Donald Hunter
 <donald.hunter@...il.com>, Eric Dumazet <edumazet@...gle.com>, Jan Stancek
 <jstancek@...hat.com>, Paolo Abeni <pabeni@...hat.com>, Ruben Wauters
 <rubenru09@....com>, joel@...lfernandes.org,
 linux-kernel-mentees@...ts.linux.dev, linux-kernel@...r.kernel.org,
 lkmm@...ts.linux.dev, netdev@...r.kernel.org, peterz@...radead.org,
 stern@...land.harvard.edu
Subject: Re: [PATCH 4/4] docs: netlink: store generated .rst files at
 Documentation/output

On Tue, 10 Jun 2025 22:59:11 +0200 Mauro Carvalho Chehab wrote:
> > The question is, are we OK with the templates that need to be created
> > for netlink specs?!   
> 
> If there's no other way, one might have a tool for maintainers to use
> to update templates, but yeah, having one template per each yaml
> is not ideal. I think we need to investigate it better and seek for
> some alternatives to avoid it.

FWIW we have tools/net/ynl/ynl-regen.sh, it regenerates the C code 
we have committed in the tree (uAPI headers mostly).
We could add it there. Which is not to distract from your main
point that not having the templates would be ideal.