All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Michal Wajdeczko" <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checksparse: success for Introduce GuC context ID Manager (rev3)
Date: Wed, 27 Mar 2024 11:52:31 -0000	[thread overview]
Message-ID: <171154035108.1055670.9040710278520173342@8e613ede5ea5> (raw)
In-Reply-To: <20240313221112.1089-1-michal.wajdeczko@intel.com>

== Series Details ==

Series: Introduce GuC context ID Manager (rev3)
URL   : https://patchwork.freedesktop.org/series/128445/
State : success

== Summary ==

+ trap cleanup EXIT
+ KERNEL=/kernel
+ MT=/root/linux/maintainer-tools
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools /root/linux/maintainer-tools
Cloning into '/root/linux/maintainer-tools'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ make -C /root/linux/maintainer-tools
make: Entering directory '/root/linux/maintainer-tools'
cc -O2 -g -Wextra -o remap-log remap-log.c
make: Leaving directory '/root/linux/maintainer-tools'
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ /root/linux/maintainer-tools/dim sparse --fast 426c7cf8b01f87def935a357bfd76712c4f03016
Sparse version: 0.6.1 (Ubuntu: 0.6.1-2build1)
Fast mode used, each commit won't be checked separately.
Okay!

+ cleanup
++ stat -c %u:%g /kernel
+ chown -R 1003:1003 /kernel



  parent reply	other threads:[~2024-03-27 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 22:11 [PATCH v2 0/4] Introduce GuC context ID Manager Michal Wajdeczko
2024-03-13 22:11 ` [PATCH v2 1/4] drm/xe/guc: Move GUC_ID_MAX definition to GuC ABI header Michal Wajdeczko
2024-03-13 22:11 ` [PATCH v2 2/4] drm/xe/guc: Introduce GuC context ID Manager Michal Wajdeczko
2024-03-26 19:17   ` Matthew Brost
2024-03-13 22:11 ` [PATCH v2 3/4] drm/xe/kunit: Add basic tests for " Michal Wajdeczko
2024-03-27 19:00   ` Matthew Brost
2024-03-13 22:11 ` [PATCH v2 4/4] drm/xe/guc: Use GuC ID Manager in submission code Michal Wajdeczko
2024-03-26 19:22   ` Matthew Brost
2024-03-27 11:36 ` ✓ CI.Patch_applied: success for Introduce GuC context ID Manager (rev3) Patchwork
2024-03-27 11:36 ` ✗ CI.checkpatch: warning " Patchwork
2024-03-27 11:37 ` ✓ CI.KUnit: success " Patchwork
2024-03-27 11:48 ` ✓ CI.Build: " Patchwork
2024-03-27 11:51 ` ✓ CI.Hooks: " Patchwork
2024-03-27 11:52 ` Patchwork [this message]
2024-03-27 12:31 ` ✓ 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=171154035108.1055670.9040710278520173342@8e613ede5ea5 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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 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.