From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rob Clark <robdclark@gmail.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Petr Vorel <pvorel@suse.cz>,
linux-arm-msm@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH v4 1/2] init/Kconfig: add python3 availability config
Date: Fri, 22 Nov 2024 16:13:37 +0200 [thread overview]
Message-ID: <878qtbz78u.fsf@intel.com> (raw)
In-Reply-To: <CAF6AEGtXEcNijTqH+NZ5-8ZX2TnzsxACJQ9XXWC9zGTJGxNv=w@mail.gmail.com>
On Fri, 22 Nov 2024, Rob Clark <robdclark@gmail.com> wrote:
> I may be biased here, but being able to generate code/tables/etc at
> build time is something that python is very useful for, and has been
> used to great effect in mesa.
Agreed. I look at the list of required dependencies, and none of the
alternatives seem more appropriate for the task. Not having to worry
about hostprogs build is a bonus.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-11-22 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 20:41 [PATCH v4 1/2] init/Kconfig: add python3 availability config Petr Vorel
2024-11-20 20:41 ` [PATCH v4 2/2] drm/msm: depend on python3 Petr Vorel
2024-11-20 21:34 ` [PATCH v4 1/2] init/Kconfig: add python3 availability config Masahiro Yamada
2024-11-21 1:17 ` Petr Vorel
2024-11-21 1:49 ` Rob Clark
2024-11-21 22:28 ` Masahiro Yamada
2024-11-22 20:41 ` Petr Vorel
2024-11-26 4:12 ` Masahiro Yamada
2024-11-21 22:16 ` Masahiro Yamada
2024-11-22 9:51 ` Jani Nikula
2024-11-22 13:49 ` Rob Clark
2024-11-22 14:13 ` Jani Nikula [this message]
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=878qtbz78u.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pvorel@suse.cz \
--cc=robdclark@gmail.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