workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: mchehab+huawei@kernel.org
Cc: corbet@lwn.net, 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: Thu, 31 Jul 2025 12:14:55 +0900	[thread overview]
Message-ID: <aa15a1f3-0efc-419a-845c-d34937eedb0f@gmail.com> (raw)
In-Reply-To: <b03b95b8d09358e81e4f27942839191f49b0ba80.1753806485.git.mchehab+huawei@kernel.org>

On Tue, 29 Jul 2025 18:43:04 +0200, Mauro Carvalho Chehab 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.
> 

OK. This sounds convincing enough.

> 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(-)
> 
> diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
> index bccfa19b45df..4c9088e429c8 100644
> --- a/Documentation/process/changes.rst
> +++ b/Documentation/process/changes.rst
> @@ -61,7 +61,7 @@ Sphinx\ [#f1]_         3.4.3            sphinx-build --version
>  GNU tar                1.28             tar --version
>  gtags (optional)       6.6.5            gtags --version
>  mkimage (optional)     2017.01          mkimage --version
> -Python (optional)      3.9.x            python3 --version
> +Python                 3.9.x            python3 --version
>  GNU AWK (optional)     5.1.0            gawk --version
>  ====================== ===============  ========================================
>  
> @@ -154,6 +154,13 @@ Perl
>  You will need perl 5 and the following modules: ``Getopt::Long``,
>  ``Getopt::Std``, ``File::Basename``, and ``File::Find`` to build the kernel.
>  
> +Python
> +------
> +
> +Several config options require it: it is required for arm/arm64
> +default configs, CONFIG_LTO_CLANG, some DRM optional configs,
> +the kernel-doc tool, and docs build (Sphinx), among others.
> +

Looks much better.  Feel free to add:

Acked-by: Akira Yokosawa <akiyks@gmail.com>

Thanks.


  reply	other threads:[~2025-07-31  3:14 UTC|newest]

Thread overview: 5+ 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 2/2] docs: changes: better document Python needs Mauro Carvalho Chehab
2025-07-31  3:14   ` Akira Yokosawa [this message]
2025-08-04 18:08   ` Rob Herring
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=aa15a1f3-0efc-419a-845c-d34937eedb0f@gmail.com \
    --to=akiyks@gmail.com \
    --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).