From: Petr Vorel <pvorel@suse.cz>
To: Masahiro Yamada <masahiroy@kernel.org>
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>
Subject: Re: [PATCH v4 1/2] init/Kconfig: add python3 availability config
Date: Thu, 21 Nov 2024 02:17:20 +0100 [thread overview]
Message-ID: <20241121011720.GA69389@pevik> (raw)
In-Reply-To: <CAK7LNASYr+pjUs-W40d_Gc+vP67nX7NHXyE0AnOpXxXgxrCtqQ@mail.gmail.com>
> On Thu, Nov 21, 2024 at 5:41 AM Petr Vorel <pvorel@suse.cz> wrote:
> > It will be used in the next commit for DRM_MSM.
> > Suggested-by: Rob Clark <robdclark@gmail.com>
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > Changes v3->v4:
> > * Move definition to the end of the file
> I prefer to not check the tool.
Ack.
> Why don't you install python3?
Everybody installs it when it's required, the question is how to inform about
the dependency.
There build environments are minimal environments:
* chroot (e.g. cross compilation)
* container
These are used by both developers and distros.
Kind regards,
Petr
> > init/Kconfig | 3 +++
> > 1 file changed, 3 insertions(+)
> > diff --git a/init/Kconfig b/init/Kconfig
> > index fbd0cb06a50a..c77e45484e81 100644
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -2047,3 +2047,6 @@ config ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
> > # <asm/syscall_wrapper.h>.
> > config ARCH_HAS_SYSCALL_WRAPPER
> > def_bool n
> > +
> > +config HAVE_PYTHON3
> > + def_bool $(success,$(PYTHON3) -V)
> > --
> > 2.45.2
next prev parent reply other threads:[~2024-11-21 1:17 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 [this message]
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
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=20241121011720.GA69389@pevik \
--to=pvorel@suse.cz \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.