public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>, Petr Vorel <pvorel@suse.cz>
Cc: 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,
	Rob Clark <robdclark@gmail.com>, Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH v4 1/2] init/Kconfig: add python3 availability config
Date: Fri, 22 Nov 2024 11:51:43 +0200	[thread overview]
Message-ID: <87h67zzjdc.fsf@intel.com> (raw)
In-Reply-To: <CAK7LNARc4Cp1a8G9p0KiCGyu0WL3BNEd0BY0COMPL4U8bLr8gA@mail.gmail.com>

On Fri, 22 Nov 2024, Masahiro Yamada <masahiroy@kernel.org> wrote:
> Documentation/process/changes.rst
> documents basic tools necessary for building the kernel.
>
> Python3 is listed as "optional" because it is required
> only for some CONFIG options.
>
> If the exact dependency is unclear, it is better to install
> all tools listed in that table.

I think we're slightly in a limbo with the python build dependency. I
think it got initially merged a bit under the radar. And I don't mean to
imply any ill will here, it just didn't get the attention it maybe
should have. The dependency table got updated afterwards.

Now, what's the status for more modules depending on python? I for one
would like to use it for i915.ko, but I'm a bit uneasy about it as long
as it's "optional". Conversely, how many more users would we need to
switch the status from "optional" to "required"?


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-11-22  9:51 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 [this message]
2024-11-22 13:49         ` Rob Clark
2024-11-22 14:13           ` 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=87h67zzjdc.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