intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jonathan Cavitt" <jonathan.cavitt@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/xe_guc_submit: Fix exec queue stop race condition
Date: Fri, 29 Mar 2024 04:46:48 -0000	[thread overview]
Message-ID: <171168760802.1066178.4762631899092286576@8e613ede5ea5> (raw)
In-Reply-To: <20240328213358.3506490-1-jonathan.cavitt@intel.com>

== Series Details ==

Series: series starting with [1/2] drm/xe/xe_guc_submit: Fix exec queue stop race condition
URL   : https://patchwork.freedesktop.org/series/131796/
State : success

== Summary ==

=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: 98f893b726e1 drm-tip: 2024y-03m-29d-01h-42m-42s UTC integration manifest
=== git am output follows ===
Applying: drm/xe/xe_guc_submit: Fix exec queue stop race condition
Applying: drm/xe/xe_guc_status: Allow lr exec queues to be banned



  parent reply	other threads:[~2024-03-29  4:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 21:33 [PATCH 1/2] drm/xe/xe_guc_submit: Fix exec queue stop race condition Jonathan Cavitt
2024-03-28 21:33 ` [PATCH 2/2] drm/xe/xe_guc_status: Allow lr exec queues to be banned Jonathan Cavitt
2024-03-29  4:46 ` Patchwork [this message]
2024-03-29  4:47 ` ✓ CI.checkpatch: success for series starting with [1/2] drm/xe/xe_guc_submit: Fix exec queue stop race condition Patchwork
2024-03-29  4:48 ` ✓ CI.KUnit: " Patchwork
2024-03-29  5:00 ` ✓ CI.Build: " Patchwork
2024-03-29  5:03 ` ✓ CI.Hooks: " Patchwork
2024-03-29  5:19 ` ✓ CI.checksparse: " Patchwork
2024-03-29  6:04 ` ✓ CI.BAT: " 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=171168760802.1066178.4762631899092286576@8e613ede5ea5 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.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;
as well as URLs for NNTP newsgroup(s).