From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Mika Kuoppala" <mika.kuoppala@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checksparse: success for !fixup: drm/xe/gsc: GSC FW load
Date: Fri, 08 Dec 2023 03:34:02 -0000 [thread overview]
Message-ID: <170200644248.7324.3175363942972409104@emeril.freedesktop.org> (raw)
In-Reply-To: <20231207205556.495523-1-mika.kuoppala@linux.intel.com>
== Series Details ==
Series: !fixup: drm/xe/gsc: GSC FW load
URL : https://patchwork.freedesktop.org/series/127526/
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 2fb92bd630cfa05b0c63fb268f0f5ebce08cce54
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-12-08 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 20:55 [PATCH] !fixup: drm/xe/gsc: GSC FW load Mika Kuoppala
2023-12-08 0:53 ` Daniele Ceraolo Spurio
2023-12-08 3:23 ` ✓ CI.Patch_applied: success for " Patchwork
2023-12-08 3:23 ` ✓ CI.checkpatch: " Patchwork
2023-12-08 3:25 ` ✓ CI.KUnit: " Patchwork
2023-12-08 3:32 ` ✓ CI.Build: " Patchwork
2023-12-08 3:32 ` ✓ CI.Hooks: " Patchwork
2023-12-08 3:34 ` Patchwork [this message]
2023-12-08 4:09 ` ✓ 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=170200644248.7324.3175363942972409104@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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