linux-kernel - Re: [PATCH v2 3/2] docs: changes: better document Python needs

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: <83d12d5293e23c622ae390204fed8fd4453014b1@intel.com>
Date: Mon, 28 Jul 2025 12:28:45 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>, Jonathan Corbet
 <corbet@....net>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>, Linux Doc Mailing
 List <linux-doc@...r.kernel.org>, linux-kernel@...r.kernel.org,
 workflows@...r.kernel.org, Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v2 3/2] docs: changes: better document Python needs

On Thu, 24 Jul 2025, Mauro Carvalho Chehab <mchehab+huawei@...nel.org> wrote:
> Em Thu, 24 Jul 2025 08:42:59 -0600
> Jonathan Corbet <corbet@....net> escreveu:
>
>> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
>> 
>> > Maybe I can place instead CONFIG_DRM_I915_WERROR.
>> 
>> I've held off on this series on the expectation that a new version would
>> come.  I guess, at this point, it will be a post-merge-window thing?
>
> Feel free to postpone. I have already a new version of it here somewhere on
> my branches, but I had to take some days off. So, I ended not sending you
> the (probably) final version.
>
> I intend to send what I have here during the merge window for you to
> review and apply post-merge-window.

I think the main questions here are 1) how to handle optional build tool
dependencies, and 2) whether Python is an optional or required
dependency.

It might be nice to be able to have an actual Kconfig and dependency for
optional tools. "depends on TOOL_PYTHON" or something. Enable the
option, and you should have Python.

This in turn raises the question for allyesconfig. It's cumbersome
(though not impossible) to add config options that you actually have to
enable manually.

The header test stuff really isn't required to actually build the kernel
or drm, however DRM_MSM does depend on Python for building the driver.

BR,
Jani.

-- 
Jani Nikula, Intel