linux-kernel - Re: [PATCH v4 12/14] MAINTAINERS: add maintainers for netlink_yml

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: <20250614103700.0be60115@kernel.org>
Date: Sat, 14 Jun 2025 10:37:00 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Donald Hunter <donald.hunter@...il.com>, Jonathan Corbet
 <corbet@....net>, Linux Doc Mailing List <linux-doc@...r.kernel.org>, Akira
 Yokosawa <akiyks@...il.com>, Breno Leitao <leitao@...ian.org>, "David S.
 Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Ignacio
 Encinas Rubio <ignacio@...cinas.com>, Jan Stancek <jstancek@...hat.com>,
 Marco Elver <elver@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Ruben
 Wauters <rubenru09@....com>, Shuah Khan <skhan@...uxfoundation.org>,
 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 v4 12/14] MAINTAINERS: add maintainers for
 netlink_yml_parser.py

On Sat, 14 Jun 2025 17:32:35 +0200 Mauro Carvalho Chehab wrote:
> > > @@ -27314,6 +27315,7 @@ M:      Jakub Kicinski <kuba@...nel.org>
> > >  F:     Documentation/netlink/
> > >  F:     Documentation/userspace-api/netlink/intro-specs.rst
> > >  F:     Documentation/userspace-api/netlink/specs.rst
> > > +F:     scripts/lib/netlink_yml_parser.py
> > >  F:     tools/net/ynl/  
> 
> With regards to the location itself, as I said earlier, it is up to
> Jon and you to decide.
> 
> My preference is to have all Python libraries at the entire Kernel
> inside scripts/lib (or at some other common location), no matter where
> the caller Python command or in-kernel Sphinx extensions are located.

I understand that from the PoV of ease of maintenance of the docs.
Is it fair to say there is a trade off here between ease of maintenance
for docs maintainers and encouraging people to integrate with kernel
docs in novel ways?