public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Michal Suchanek <msuchanek@suse.de>
Cc: linux-kbuild@vger.kernel.org, Nicolas Schier <nsc@kernel.org>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: dummy-tools: Add python3
Date: Wed, 21 Jan 2026 16:16:51 -0700	[thread overview]
Message-ID: <20260121231651.GA601114@ax162> (raw)
In-Reply-To: <20260121105801.1827-1-msuchanek@suse.de>

On Wed, Jan 21, 2026 at 11:57:57AM +0100, Michal Suchanek wrote:
> DRM_MSM_VALIDATE_XML depends on a python feature. Add a dummy python
> interpreter to make it possible to configure this option with dummy
> tools.
> 
> Fixes: b587f413ca47 ("drm/msm/gen_header: allow skipping the validation")
> Signed-off-by: Michal Suchanek <msuchanek@suse.de>

Sure, this seems reasonable, as Python may become more used for various
parts of the kernel over time.

I was thinking this could qualify as a fix for Nicolas to take now but
the help text of CONFIG_DRM_MSM_VALIDATE_XML mentions this option is
mostly targeted at drm/msm developers, so we can probably just take this
via kbuild-next.

> ---
>  scripts/dummy-tools/python3 | 5 +++++
>  1 file changed, 5 insertions(+)
>  create mode 100755 scripts/dummy-tools/python3
> 
> diff --git a/scripts/dummy-tools/python3 b/scripts/dummy-tools/python3
> new file mode 100755
> index 000000000000..1f3ac6541dd3
> --- /dev/null
> +++ b/scripts/dummy-tools/python3
> @@ -0,0 +1,5 @@
> +#!/bin/sh
> +# SPDX-License-Identifier: GPL-2.0-only
> +#
> +
> +true
> -- 
> 2.51.0
> 

  reply	other threads:[~2026-01-21 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 10:57 [PATCH] kbuild: dummy-tools: Add python3 Michal Suchanek
2026-01-21 23:16 ` Nathan Chancellor [this message]
2026-01-22  3:31   ` Rob Clark
2026-01-30  0:17 ` Nathan Chancellor
2026-02-04  7:10   ` Masahiro Yamada
2026-02-04  7:45     ` Nathan Chancellor
2026-02-04  8:16       ` Masahiro Yamada

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=20260121231651.GA601114@ax162 \
    --to=nathan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=msuchanek@suse.de \
    --cc=nsc@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robin.clark@oss.qualcomm.com \
    /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