mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: linux-kbuild@vger.kernel.org, Michal Suchanek <msuchanek@suse.de>
Cc: Nathan Chancellor <nathan@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: Thu, 29 Jan 2026 17:17:37 -0700	[thread overview]
Message-ID: <176973225791.178709.17831414346066426792.b4-ty@kernel.org> (raw)
In-Reply-To: <20260121105801.1827-1-msuchanek@suse.de>

On Wed, 21 Jan 2026 11:57:57 +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.
> 
> 

Applied to

  https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next

Thanks!

[1/1] kbuild: dummy-tools: Add python3
      https://git.kernel.org/kbuild/c/76c73cfde7988

Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.

Best regards,
-- 
Nathan Chancellor <nathan@kernel.org>


  parent reply	other threads:[~2026-01-30  0:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 10:57 Michal Suchanek
2026-01-21 23:16 ` Nathan Chancellor
2026-01-22  3:31   ` Rob Clark
2026-01-30  0:17 ` Nathan Chancellor [this message]
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=176973225791.178709.17831414346066426792.b4-ty@kernel.org \
    --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

all inboxes | Powered by JetHome®