From: Vignesh Raman <vignesh.raman@collabora.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: dri-devel@lists.freedesktop.org, daniels@collabora.com,
helen.fornazier@gmail.com, airlied@gmail.com,
simona.vetter@ffwll.ch, robdclark@gmail.com,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
valentine.burley@collabora.com, jani.nikula@linux.intel.com,
dmitry.baryshkov@linaro.org, mripard@kernel.org,
boqun.feng@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] drm/ci: enable lockdep detection
Date: Wed, 12 Mar 2025 08:36:13 +0530 [thread overview]
Message-ID: <46f78829-a65a-4cd9-b35a-7608e547096d@collabora.com> (raw)
In-Reply-To: <CAPj87rNUMDMUtrfV=8c_+T5VQ0FykjpR5JW5dgO4grYXpabSdQ@mail.gmail.com>
Hi Daniel,
On 10/03/25 13:53, Daniel Stone wrote:
> Hi Vignesh,
>
> On Mon, 17 Feb 2025 at 05:37, Vignesh Raman <vignesh.raman@collabora.com> wrote:
>> This patch series enables lockdep detection in drm-ci. Any lockdep
>> failures will be shown as warnings in the pipeline. This series
>> also enables CONFIG_DEBUG_WW_MUTEX_SLOWPATH for mutex slowpath
>> debugging and refactors software-driver stage jobs.
>>
>> Test run with this series,
>> https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1366054
>
> Series is:
> Reviewed-by: Daniel Stone <daniels@collabora.com>
>
> Please merge at will.
applied to drm-misc-next
Regards,
Vignesh
>
> Cheers,
> Daniel
prev parent reply other threads:[~2025-03-12 3:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 5:37 Vignesh Raman
2025-02-17 5:37 ` [PATCH v3 1/3] drm/ci: refactor software-driver stage jobs Vignesh Raman
2025-02-26 20:23 ` Helen Mae Koike Fornazier
2025-02-17 5:37 ` [PATCH v3 2/3] drm/ci: enable CONFIG_DEBUG_WW_MUTEX_SLOWPATH Vignesh Raman
2025-02-26 20:22 ` Helen Mae Koike Fornazier
2025-02-17 5:37 ` [PATCH v3 3/3] drm/ci: enable lockdep detection Vignesh Raman
2025-02-26 20:24 ` Helen Mae Koike Fornazier
2025-03-10 8:23 ` [PATCH v3 0/3] " Daniel Stone
2025-03-12 3:06 ` 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=46f78829-a65a-4cd9-b35a-7608e547096d@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=valentine.burley@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®