From: Jon Hunter <jonathanh@nvidia.com>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Jonathan Corbet <corbet@lwn.net>, Rob Clark <robdclark@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH v2] docs: document python version used for compilation
Date: Mon, 13 May 2024 09:50:04 +0100 [thread overview]
Message-ID: <0c6af8ed-3cd5-4037-a232-3f697d448573@nvidia.com> (raw)
In-Reply-To: <68e05c6f-d0ed-efea-6eef-a9ee008c6c24@quicinc.com>
On 12/05/2024 00:52, Abhinav Kumar wrote:
>
>
> On 5/11/2024 3:32 PM, Dmitry Baryshkov wrote:
>> The drm/msm driver had adopted using Python3 script to generate register
>> header files instead of shipping pre-generated header files. Document
>> the minimal Python version supported by the script. Per request by Jon
>> Hunter, the script is required to be compatible with Python 3.5.
>>
>> Python is documented as an optional dependency, as it is required only
>> in a limited set of kernel configurations (following the example of
>> other optional dependencies).
>>
>> Cc: Jon Hunter <jonathanh@nvidia.com>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> ---
>> Depends:
>> https://lore.kernel.org/dri-devel/20240507230440.3384949-1-quic_abhinavk@quicinc.com/
>> ---
>> Changes in v2:
>> - Expanded documentation for the Python usage.
>> - Link to v1:
>> https://lore.kernel.org/r/20240509-python-version-v1-1-a7dda3a95b5f@linaro.org
>> ---
>> Documentation/process/changes.rst | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>
>
> Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Thanks! I made a request to update some of our legacy builders and so
hopefully they might be upgraded to a newer version. Anyway ...
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
prev parent reply other threads:[~2024-05-13 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 22:32 [PATCH v2] docs: document python version used for compilation Dmitry Baryshkov
2024-05-11 23:52 ` Abhinav Kumar
2024-05-13 8:50 ` Jon Hunter [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=0c6af8ed-3cd5-4037-a232-3f697d448573@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=corbet@lwn.net \
--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-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=masahiroy@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=workflows@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).