From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Arun R Murthy" <arun.r.murthy@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.Patch_applied: success for drm/xe/display: check for error on drmm_mutex_init (rev3)
Date: Thu, 28 Mar 2024 08:15:13 -0000 [thread overview]
Message-ID: <171161371328.1061727.5270346799452559468@8e613ede5ea5> (raw)
In-Reply-To: <20240328080005.410961-1-arun.r.murthy@intel.com>
== Series Details ==
Series: drm/xe/display: check for error on drmm_mutex_init (rev3)
URL : https://patchwork.freedesktop.org/series/131300/
State : success
== Summary ==
=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: 8d398ffc40ac drm-tip: 2024y-03m-28d-08h-07m-15s UTC integration manifest
=== git am output follows ===
Applying: drm/xe/display: check for error on drmm_mutex_init
next prev parent reply other threads:[~2024-03-28 8:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 8:00 [PATCHv2] drm/xe/display: check for error on drmm_mutex_init Arun R Murthy
2024-03-28 8:15 ` Patchwork [this message]
2024-03-28 8:15 ` ✓ CI.checkpatch: success for drm/xe/display: check for error on drmm_mutex_init (rev3) Patchwork
2024-03-28 8:16 ` ✓ CI.KUnit: " Patchwork
2024-03-28 8:31 ` [PATCHv2] drm/xe/display: check for error on drmm_mutex_init Andi Shyti
2024-03-28 10:33 ` Jani Nikula
2024-03-28 10:45 ` Andi Shyti
2024-03-28 10:55 ` Murthy, Arun R
2024-03-28 11:07 ` Andi Shyti
2024-03-30 12:05 ` Murthy, Arun R
2024-04-03 15:32 ` Lucas De Marchi
2024-03-28 8:34 ` ✓ CI.Build: success for drm/xe/display: check for error on drmm_mutex_init (rev3) Patchwork
2024-03-28 8:37 ` ✓ CI.Hooks: " Patchwork
2024-03-28 8:38 ` ✓ CI.checksparse: " Patchwork
2024-03-28 9:22 ` ✓ CI.BAT: " Patchwork
2024-03-28 15:23 ` ✓ Fi.CI.BAT: " Patchwork
2024-03-28 17:48 ` ✓ Fi.CI.IGT: " Patchwork
2024-03-28 22:46 ` ✗ Fi.CI.IGT: failure " Patchwork
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=171161371328.1061727.5270346799452559468@8e613ede5ea5 \
--to=patchwork@emeril.freedesktop.org \
--cc=arun.r.murthy@intel.com \
--cc=intel-xe@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.