linux-kernel - Re: [PATCH] drm/ci: uprev mesa version: fix kdl commit fetch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Thu, 21 Dec 2023 19:56:04 +0530
From: Vignesh Raman <vignesh.raman@...labora.com>
To: Helen Koike <helen.koike@...labora.com>,
 Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: daniels@...labora.com, emma@...olt.net, freedreno@...ts.freedesktop.org,
 guilherme.gallo@...labora.com, sergi.blanch.torne@...labora.com,
 dri-devel@...ts.freedesktop.org, quic_abhinavk@...cinc.com,
 david.heidelberg@...labora.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/ci: uprev mesa version: fix kdl commit fetch

Hi,

On 14/12/23 17:50, Helen Koike wrote:
> 
> 
> On 14/12/2023 05:00, Dmitry Baryshkov wrote:
>> On Tue, 12 Dec 2023 at 18:04, Vignesh Raman 
>> <vignesh.raman@...labora.com> wrote:
>>>
>>> build-kdl.sh was doing a `clone --depth 1` of the default branch,
>>> then checking out a commit that might not be the latest of that
>>> branch, resulting in container build error.
>>>
>>> https://gitlab.freedesktop.org/mesa/mesa/-/commit/5efa4d56 fixes
>>> kdl commit fetch issue. Uprev mesa in drm-ci to fix this.
>>>
>>> This commit also updates the kernel tag and adds .never-post-merge-rules
>>> due to the mesa uprev.
>>>
>>> Tested-by: Abhinav Kumar <quic_abhinavk@...cinc.com>
>>> Signed-off-by: Vignesh Raman <vignesh.raman@...labora.com>
>>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
> 
> Acked-by: Helen Koike <helen.koike@...labora.com>
> 

With this mesa uprev, the virtio-gpu jobs are not getting created and
other jobs are not affected. The issue is identified and fixed, will be 
sending a v2.

Regards,
Vignesh