mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: Helen Koike <helen.koike@collabora.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: daniels@collabora.com, emma@anholt.net,
	freedreno@lists.freedesktop.org, guilherme.gallo@collabora.com,
	sergi.blanch.torne@collabora.com,
	dri-devel@lists.freedesktop.org, quic_abhinavk@quicinc.com,
	david.heidelberg@collabora.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/ci: uprev mesa version: fix kdl commit fetch
Date: Thu, 21 Dec 2023 19:56:04 +0530	[thread overview]
Message-ID: <981a49d2-19ed-21fb-77af-ba9684a60cc3@collabora.com> (raw)
In-Reply-To: <e747581b-d5e0-4622-827b-48fb51fa9711@collabora.com>

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@collabora.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@quicinc.com>
>>> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
>>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> 
> Acked-by: Helen Koike <helen.koike@collabora.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

      reply	other threads:[~2023-12-21 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 16:04 Vignesh Raman
2023-12-14  8:00 ` Dmitry Baryshkov
2023-12-14 12:20   ` Helen Koike
2023-12-21 14:26     ` Vignesh Raman [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=981a49d2-19ed-21fb-77af-ba9684a60cc3@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=daniels@collabora.com \
    --cc=david.heidelberg@collabora.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=freedreno@lists.freedesktop.org \
    --cc=guilherme.gallo@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=sergi.blanch.torne@collabora.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®