[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e043ff3-58e0-7fd0-00b6-9117bc81e9ff@quicinc.com>
Date: Thu, 9 May 2024 11:59:52 -0700
From: Abhinav Kumar <quic_abhinavk@...cinc.com>
To: Jonathan Corbet <corbet@....net>,
Dmitry Baryshkov
<dmitry.baryshkov@...aro.org>,
Rob Clark <robdclark@...il.com>, Sean Paul
<sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>
CC: <workflows@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Masahiro Yamada <masahiroy@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<freedreno@...ts.freedesktop.org>
Subject: Re: [PATCH] docs: document python version used for compilation
On 5/9/2024 9:48 AM, Jonathan Corbet wrote:
> Dmitry Baryshkov <dmitry.baryshkov@...aro.org> writes:
>
>> 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.
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
>> ---
>> Documentation/process/changes.rst | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
>> index 5685d7bfe4d0..8d225a9f65a2 100644
>> --- a/Documentation/process/changes.rst
>> +++ b/Documentation/process/changes.rst
>> @@ -63,6 +63,7 @@ cpio any cpio --version
>> GNU tar 1.28 tar --version
>> gtags (optional) 6.6.5 gtags --version
>> mkimage (optional) 2017.01 mkimage --version
>> +Python (optional) 3.5.x python3 --version
>> ====================== =============== ========================================
>
> Is it really optional - can you build the driver without it?
>
True, we cannot build the driver now without it. So we should be
dropping the optional tag.
With that addressed,
Reviewed-by: Abhinav Kumar <quic_abhinavk@...cinc.com>
> This document needs some help... I'm missing a number of things that are
> *not* marked as "optional" (jfsutils, reiserfsprogs, pcmciautils, ppp,
> ...) and somehow my system works fine :) It would be nice to document
> *why* users might need a specific tool.
>
> But I guess we aren't going to do that now. I can apply this, but I do
> wonder about the "optional" marking.
>
> Thanks,
>
> jon
Powered by blists - more mailing lists