Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniele Ceraolo Spurio" <daniele.ceraolospurio@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.Patch_applied: success for drm/xe: Always check force_wake_get return code (rev3)
Date: Tue, 04 Jun 2024 16:46:14 -0000	[thread overview]
Message-ID: <171751957438.2263376.1785750428654269009@8e613ede5ea5> (raw)
In-Reply-To: <20240603113005.710746-1-tejas.upadhyay@intel.com>

== Series Details ==

Series: drm/xe: Always check force_wake_get return code (rev3)
URL   : https://patchwork.freedesktop.org/series/131045/
State : success

== Summary ==

=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: d3a2b947894e drm-tip: 2024y-06m-04d-15h-48m-13s UTC integration manifest
=== git am output follows ===
Applying: drm/xe: Always check force_wake_get return code



  parent reply	other threads:[~2024-06-04 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 11:30 [PATCH] drm/xe: Always check force_wake_get return code Tejas Upadhyay
2024-06-03 18:56 ` Daniele Ceraolo Spurio
2024-06-03 19:39   ` Lucas De Marchi
2024-06-04 18:31     ` Rodrigo Vivi
2024-06-04 16:46 ` Patchwork [this message]
2024-06-04 16:46 ` ✓ CI.checkpatch: success for drm/xe: Always check force_wake_get return code (rev3) Patchwork
2024-06-04 16:47 ` ✓ CI.KUnit: " Patchwork
2024-06-04 16:58 ` ✓ CI.Build: " Patchwork
2024-06-04 16:59 ` ✗ CI.Hooks: failure " Patchwork
2024-06-04 17:00 ` ✓ CI.checksparse: success " Patchwork
2024-06-04 17:24 ` ✓ CI.BAT: " Patchwork
2024-06-04 21:01 ` ✗ CI.FULL: 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=171751957438.2263376.1785750428654269009@8e613ede5ea5 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniele.ceraolospurio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox