From: Jani Nikula <jani.nikula@intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2 3/2] docs: changes: better document Python needs
Date: Mon, 28 Jul 2025 12:28:45 +0300 [thread overview]
Message-ID: <83d12d5293e23c622ae390204fed8fd4453014b1@intel.com> (raw)
In-Reply-To: <20250724194306.27b98194@foz.lan>
On Thu, 24 Jul 2025, Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> Em Thu, 24 Jul 2025 08:42:59 -0600
> Jonathan Corbet <corbet@lwn.net> escreveu:
>
>> Mauro Carvalho Chehab <mchehab+huawei@kernel.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
next prev parent reply other threads:[~2025-07-28 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1752307866.git.mchehab+huawei@kernel.org>
2025-07-12 8:32 ` Mauro Carvalho Chehab
2025-07-12 16:31 ` Laurent Pinchart
2025-07-12 22:25 ` Mauro Carvalho Chehab
2025-07-13 9:27 ` Laurent Pinchart
2025-07-24 14:42 ` Jonathan Corbet
2025-07-24 17:43 ` Mauro Carvalho Chehab
2025-07-28 9:28 ` Jani Nikula [this message]
2025-07-28 15:33 ` Mauro Carvalho Chehab
2025-07-29 10:45 ` Jani Nikula
2025-07-29 13:44 ` Mauro Carvalho Chehab
2025-07-29 15:04 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d12d5293e23c622ae390204fed8fd4453014b1@intel.com \
--to=jani.nikula@intel.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox