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: <877c17h4wt.fsf@trenco.lwn.net>
Date: Thu, 19 Jun 2025 14:06:58 -0600
From: Jonathan Corbet <corbet@....net>
To: Jakub Kicinski <kuba@...nel.org>, Mauro Carvalho Chehab
 <mchehab+huawei@...nel.org>
Cc: Donald Hunter <donald.hunter@...il.com>, 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

Jakub Kicinski <kuba@...nel.org> writes:

> On Sat, 14 Jun 2025 20:56:09 +0200 Mauro Carvalho Chehab wrote:

>> I'm more interested on having a single place where python libraries
>> could be placed.
>
> Me too, especially for selftests. But it's not clear to me that
> scripts/ is the right location. I thought purely user space code
> should live in tools/ and bulk of YNL is for user space.

I've been out wandering the woods and canyons with no connectivity for a
bit, so missed this whole discussion, sorry.

Mauro and I had talked about the proper home for Python libraries when
he reworked kernel-doc; we ended up with them under scripts/, which I
didn't find entirely pleasing.  If you were to ask me today, I'd say
they should be under lib/python, but tomorrow I might say something
else...

In truth, I don't think it matters much, but I *do* think we should have
a single location from which to import kernel-specific Python code.
Spreading it throughout the tree just isn't going to lead to joy.

Thanks,

jon