linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	 linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH v2 2/2] docs: changes: better document Python needs
Date: Mon, 4 Aug 2025 13:08:19 -0500	[thread overview]
Message-ID: <CAL_JsqJV4JgWMn+w7XFX=ixnwWW=_buisp0fF_B-2NmbpmMTqw@mail.gmail.com> (raw)
In-Reply-To: <b03b95b8d09358e81e4f27942839191f49b0ba80.1753806485.git.mchehab+huawei@kernel.org>

On Tue, Jul 29, 2025 at 11:44 AM Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Python is listed as an optional dependency, but this is not
> true, as:
>
> 1) arm (multi_v7_defconfig and other defconfigs) and arm64 defconfig
>    needs it due to DRM_MSM dependencies;
>
> 2) CONFIG_LTO_CLANG runs a python script at scripts/Makefile.vmlinux_o;
>
> 3) kernel-doc is called during compilation when some DRM options
>    like CONFIG_DRM_I915_WERROR are enabled;
>
> 4) allyesconfig/allmodconfig will enable CONFIG_* dependencies
>    that needs it;
>
> 5) besides DRM, other subsystems seem to have logic calling *.py
>    scripts.
>
> So, better document that and change the dependency from optional
> to mandatory to reflect the current needs.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  Documentation/process/changes.rst | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)

DT schema checks requires it too.

Acked-by: Rob Herring (Arm) <robh@kernel.org>

  parent reply	other threads:[~2025-08-04 18:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 16:43 [PATCH v2 0/2] Better handle and document Python needs for Kernel build Mauro Carvalho Chehab
2025-07-29 16:43 ` [PATCH v2 1/2] docs: kernel-doc: avoid script crash on ancient Python Mauro Carvalho Chehab
2025-07-29 16:43 ` [PATCH v2 2/2] docs: changes: better document Python needs Mauro Carvalho Chehab
2025-07-31  3:14   ` Akira Yokosawa
2025-08-04 18:08   ` Rob Herring [this message]
2025-08-11 16:58 ` [PATCH v2 0/2] Better handle and document Python needs for Kernel build Jonathan Corbet

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='CAL_JsqJV4JgWMn+w7XFX=ixnwWW=_buisp0fF_B-2NmbpmMTqw@mail.gmail.com' \
    --to=robh@kernel.org \
    --cc=corbet@lwn.net \
    --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;
as well as URLs for NNTP newsgroup(s).