From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Rodrigo Vivi" <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] ✓ CI.checksparse: success for drm/xe/uapi: Kill exec_queue_set_property
Date: Wed, 29 Nov 2023 19:17:46 -0000 [thread overview]
Message-ID: <170128546666.12091.7110449335851072128@emeril.freedesktop.org> (raw)
In-Reply-To: <20231129164115.18384-1-rodrigo.vivi@intel.com>
== Series Details ==
Series: drm/xe/uapi: Kill exec_queue_set_property
URL : https://patchwork.freedesktop.org/series/127064/
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 c0de8043414d48c69a2f94bbd12cac1c1c4a19af
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
next prev parent reply other threads:[~2023-11-29 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 16:41 [Intel-xe] [RFC] drm/xe/uapi: Kill exec_queue_set_property Rodrigo Vivi
2023-11-29 19:07 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-11-29 19:07 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-29 19:08 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-29 19:16 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-29 19:16 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-29 19:17 ` Patchwork [this message]
2023-11-29 19:55 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-11-29 20:10 ` [Intel-xe] [RFC] " Souza, Jose
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=170128546666.12091.7110449335851072128@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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.